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

Like I mentioned before, depending on who you talk to, some will say free-form 
is the greatest thing that happen to RPG but other will say it is the most 
convoluted RPG coding he/she ever seen.

I think what make RPG successful is because it provides an easy way to access 
database (chain, read, setll..) not because it is simple.  I still remember the 
first time I encountered a RPG cycle program, confusing, confusing.

Hopefully you are using RPG IV already. If you are, do you really want to go 
back to RPGIII?






-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Jderham2@xxxxxx
Sent: Sunday, May 16, 2004 6:36 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Compile error when using field in a subfield data structure


Remember gentleman, the KISS principal has been the single most important 
attribute to keep RPG as leading application production tool. Yes, we want 
progress where needed but I don't think we have to take a Ph.D. approach to all 
things just because it gives some academic joy. I learned a lesson on the s/360 
when I realized that only about 10% of the instructions were ever used to build 
97% of all the applications developed.  It's nice to have a few trivia items 
for your journal but let make these new "Progressive Changes" in the form of 
API's and don't clutter up the local landscape.

Jack Derham
Direct Systems, Inc.