Re: C bug of the day

[Wesley Groleau <wesgroleau@despammed.com>]

 >
 > One point where I'm pretty sure Ada 83 didn't have the right default
 > (although they may have fixed it in Ada 95): garbage collection.  While
 > there are places where it is necessary to turn garbage collection off
 > (which seriously limits the use of a language in which you cannot have
 > untraced pointers, which the garbage collector cannot see), the safe
 > option is obviously to have it on by default, no?

In Ada, GC is automatic for stack variables, but it
was intentionally left up to the vendor for access types
(which in Ada only exist when the programmer explicitly
declares them) because in some applications, it could
cause timing problems.  However, Ada 95 did add the ability
for the programmer to define whether GC occurs for any particular
data type, as well as to define how it occurs.

 > 2) you can generally "work around" the safety checks if necessary
 > (hopefully on a case by case basis, using source code constructs;
 > e.g. by writing array.unsafe_at( index ) rather than array[ index ]).

Actually, it's something like
pragma Suppress ( <type-of-check>, <entity> );


      [ Send an empty e-mail to c++-help@netlab.cs.rpi.edu for info ]
      [ about comp.lang.c++.moderated. First time posters: do this! ]