RE: Strategic Java Usage/Productivity

["Hall, Philip" <phall@xxxxxxxx>]

> -----Original Message-----
> From: Dieter Bender [mailto:dieter.bender@xxxxxxxxxxxx]
> Subject: Re: Strategic Java Usage/Productivity
> 
> Yes, that's one approach, but this way you get only one instance for this
> program.
> 
> With the rpg implementation I have the limitation to have only one
> FileInputStream, one FileOutputStream and only one PropertyFile at the
> same time and its rather difficult to controll the lifetime of the
> instances.

Back at the release of V2R3 (the first ILE/RPG release) I (in a previous 
existence for another company) was doing the whole RPG-OO thing.

The head start I had was we ported a whole framework that we had written in C 
that actually managed the class/instance instantiation of our 'classes'. The 
frame work maintained the class and instance data and passed the data on each 
'method' call to the object. It was much faster (performance wise) than it 
sounds. The *only* thing we had to do to the RPG versions of the class objects 
was to modify the *SRVPGM (our classes were in *SRVPGM objects) object to 
remove the system check for recursive entry into a function (RPG has this 
limitation and I believe ILE/COBOL does too) - we provided a program that users 
use to do the modification after the standard compile and creation of a *SRVPGM.

--phil