It was been > 20 years since I did any C or Assembler, and never C# or Java so maybe someone could explain to me why things like "memory leaks" and "buffer overflows" seem to be more topical in those languages and Wintel platforms than here?
I know the system i can have them (I actually read many, well some, of the PTF cover letters) and so can RPG IV if you work real hard at it.
In brief my impression (correct me if I am in error) is that C, C#, Java, etc., are more prone to such problems. In other words, we have to work our tails off to actually cause these problems whereas the Wintel crowd has to constantly guard against such things. If that is a valid impression, then I can certainly understand Steve's concern; if I had to work around that scenario in every program I wrote, I'd be jittery, too.
Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Aaron Bartell
Sent: Wednesday, June 18, 2008 11:34 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Is RPG 'DEAD"
In RPG if an *escape message is sent to a procedure lower on the
invocation stack, your on-error ... endmon code will not be executed.
I won't argue that it isn't as feature rich, but could you provide an
example of the ON-ERROR not be executed? I use MONITOR *a lot* in my code
to pass custom errors.
I think activation groups hide what are in fact memory leaks (allocated
memory which is not freed ).
We need a little more than that. Sounds like you haven't done your
research.
Aaron Bartell
http://mowyourlawn.com
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/rpg400-l.
midrange.com
