Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Bob Rusk — — source: Informix-list mailing list archive (1991-1998)
<bpayne@netcom.com> (Bob Payne) wrote:
[...]
>2) r4gl will do bounds checking on variables. c4gl and i4gl will not.
> If you programmatically overrun the bound of your variables in r4gl,
> no harm done. But if you do it in c4gl/i4gl, you will either over-
> write whatever is stored in memory next to it or you will try to
> write to storage that you can't get to (segmentation violation).
Not entirely and dependably true. In at least one version of r4gl (was
it 4.00 or 4.10?) I wrote past the end of an array and clobbered some other
variables. I was kinda suprised that fglgo didn't catch it, but it didn't.
Bob Rusk
rrusk@fll-ro.DHL.COM
Your privacy choices
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.