RE: Eric DeLong solves the "Corrupted timestamp" problem and wins the prize!

That assumes a higher level of DWIM than I'd expect.  I got burned on this a
couple of years ago with a routine to center text in a field of (relatively)
arbitrary length that took a variable length text string as a parm.

> -----Original Message-----
> From: Reeve Fritchman [mailto:reeve@ltl400.com]
> Sent: Tuesday, October 23, 2001 1:02 PM
> To: Rpg400-L@Midrange. Com
> Subject: Eric DeLong solves the "Corrupted timestamp" problem and wins
> the prize!
>
>
> This is a multi-part message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> A prototype (ZZR030PR) and subprocedure (ZZR030) had
> "varying" instead of
> "value", and something overflowed into the timestamp.
>
> This raises an interesting question: should the compiler have
> spotted this
> error, or at least built a large enough buffer to prevent
> crash-and-burn?
> If I was working with pointers, I'd expect to hose myself.
> But since the
> compiler is (supposed to be) doing the housekeeping, is it
> reasonable to
> expect a safety net from RPG?
>
> Thanks, Eric...