RE: Is RPG 'DEAD"

I have no problem with explaining what you mean but you can't re-define
existing terms to satisfy your requirements. There is absolutely no
connection between a memory leak and freeing storage.

A memory leak is where a program overwrites memory to which it should not
have access. Worse case scenario being where it overwrites runnable code in
memory (as happened or earlier versions of Windows but happens a lot less
now)

Freeing storage is returning storage that the program determines is no
longer required.

Absolutely no connection between the two except that they both relate to
memory.

Personally, I trust the way the OS manages memory and I have the greatest
confidence in its ability to page the required memory for my programs
without overloading the system - I only get concerned when I am using Java
or C.

Regards

Paul Tuohy
ComCon
www.comconadvisor.com
www.systemideveloper.com


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Steve Richter
Sent: 18 June 2008 18:01
To: RPG programming on the AS400 / iSeries
Subject: Re: Is RPG 'DEAD"

On Wed, Jun 18, 2008 at 12:25 PM, Paul Tuohy <tuohyp@xxxxxxxxxxxxxxxxx>
wrote:

I must be missing something - how is a memory leak = allocated memory

which

is not freed?

just defining my terms.

And AG memory may be freed using RCLACTGRP or the relevant CEE API - or

use

AG *NEW to have it happen automatically?

right, and the shutting down of the activation group also closes files
and clears static variables. The activation groups work well but
they also add complexity to applications. The COBOL STOP RUN statement
comes to mind in this regard.

My main point is you cant have the .NET framework or Java class
library without managed code/garbage collection. C++ tried and the
result was something with too many moving parts to be of use in
commercial applications. Without framework classes, a language is
destined for the legacy heap.

-Steve