John Baker <baker-j@ix.netcom.com> wrote:
> Overrun an array boundary, clobber memory and cause a bug that doesn't
> have anything to do with the code near it? :)
Not (quite) true. Inform stores code in "high memory", which cannot be
written to. Most C implementations arrange to store C code in read-only
memory so that the code cannot be accidentally corrupted (although there
are probably some low-end rip-off merchants who sell C compilers that
don't do this).
However, in either C or Inform it is easily to run of the end of an
array and clobber other bits of dynamic data (though C makes it trivial
for you to shoot yourself in the foot by providing the gets function).
Followups to comp.lang.c
-- Gareth Rees