[Info-vax] Whither VMS?

[Paul Raulerson]

Not really Paul, most of it is just "the voice of experience" kind of  
stuff.
C is a really simple language, and though people may argue about it,
it is really very much like PDP-11 Macro assembler. You can get yourself
into trouble by not understanding what you are doing, but to compensate
for that, you can pretty much do *anything* you want to do.

Buffer over-runs can be a concern, and where they *are* a concern,
then use a different technique. :)

-Paul


On Oct 5, 2009, at 7:22 AM, P. Sture wrote:

> In article <habq5n$pi6$3 at naig.caltech.edu>,
> glen herrmannsfeldt <gah at ugcs.caltech.edu> wrote:
>
>> Michael Kraemer <M.Kraemer at gsi.de> wrote:
>> < glen herrmannsfeldt schrieb:
>>
>> <> Well, the C gets() function, I believe still part of the standard,
>> <> has no way to know the length of the buffer.  The only answer is
>> <> not to use it, but it does seem fair to blame the language in that
>> <> case.
>>
>> < To be nitpicking: it's not part of the language,
>> < neither are all other functions.
>> < But I agree, at least the doc's should deprecate its use.
>>
>> I have seen that discussed.  There are some questions in K&R as
>> to the library being part of the language.  Most agree that it is
>> for ANSI C.
>>
>> <> Otherwise, yes, it is up to programmers to check at the
>> <> appropriate points.
>>
>> And to always use fgets() instead of gets().
>>
>
> Is there a handy reference to this stuff? I mean a summary of what C
> calls to avoid and why (possibly detailing safe and unsafe
> circumstances).
>
> -- 
> Paul Sture
> _______________________________________________
> Info-vax mailing list
> Info-vax at rbnsn.com
> http://rbnsn.com/mailman/listinfo/info-vax_rbnsn.com
>