RE: Compile error when using field in a subfield data structure

The practice might have went out of style 15 years ago.  However, I think most 
RPG programmers still tend to create large program that handlers everything 
that is defined in a project.  At least I'm.  Just can't resist the temptation.

I think that is because traditionally RPG doesn't support modular programming.  
Although a lot of shops have been using RPGIV for while now, but most of them 
still doesn't allow/use modular programming.  Some shops doesn't even allow 
service program.


I agree with you that IBM has made it hard for us to transition to free-form 
due to some restrictions.  For me, mixing fix and free is just wrong.  I think 
IBM should have created a new source type like xRPG that is completely 
free-form.  This will break the burden for the IBM-RPG-compiler team of having 
to support both fix and free format in one compiler. 

I believe free-form will give IBM-RPG-compiler team more leg room to add more 
power and useful functions to RPG.  In long run, should benefit us.  I love 
%kds, but I think it would be hard for RPG compiler team to support it in fix 
form (not sure if that is the reason that it is not supported in fix form).  



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Joe Pluta
> "We conclude that in a large program, no
> indentation would be a real hindrance and very difficult to use. The
> same is true for overly indented programs."

In a large program.  By which they mean the entire program is one large
mainline, a programming practice that went out of style at least 15
years ago. 


> I can personally attest to that, working regularly with both properly
> indented C code and with traditional "straight-line" RPG code. There's
> no question at all which is easier to work with.

For you, Hans.  Many programmers find it just as easy to be able to look
at fixed-format RPG and be able to read it.  This is a style issue, not
an absolute, and there is no sound business reason for moving to /free,
especially with the artificial hurdles imposed by the RPG team.

Had the RPG team chosen to follow standard IBM practices and allow us a
clean migration path (something they could STILL do), then I believe the
uptake would be more than we see now.  It is the artificial limitations
of /free that slow its acceptance more than the intransigence of the
programmers.

Joe