Re: scope and/or parameters (beginner)

[Hyman Rosen <hymie@prolifics.com>]

Robert Dewar wrote:
> You also have to consider the knowledge base, i.e. do
> programmers know all the relatively new stuff in the ANSI
> C standard, and can they count on maintenance programmers
> to know it.
> 
> When it comes to const, this is of course an important
> feature, but it does not BEGIN to have become standard
> practice in C code, and indeed virtually all API's I
> have worked with seem to prefer to use #define in the
> traditional manner to using const. This is not a decision
> I approve of, I am merely making an observation, it takes
> time for things to change.

I don't think that the dearth of const in C code is because of lack
of knowledge. The problem with const is that it is infectious where
it is most needed, with respect to pointers. Once an object is const,
pointers to that object can not be passed as parameters to routines
which expect non-const pointers (unless casts are used). Unfortunately,
many APIs predate const, and so use non-const pointers even when they
do not modify the pointed-to data.

As far as const-vs.-#define, you cannot use const objects as parts of
constant expressions in C. (You can in C++.) The best way to declare
integer constants in C is through enum.