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

Having a varied development background, PC, 400, ES900 in everything from dBase 
to FoxPro to VB to C to RPG to COBOL to etc... I just don't see the big deal 
with using and/or intermingling free form, nor ++ -- etc..... Using regular or 
free form or subprocedures or subroutines, and so on, in RPG doesn't 
necessarily make you a better programmer, though it may allow you to do more 
with less. It's all a matter of style and/or taste. The clincher is an RPG 
shops policies and standards, which pretty much come down to a Majority 
Rule/Minority Rights situation. Does the Majority that wants to keep coding in 
familiar fashion outweigh the rights of the Minority who may, or may not, have 
the foresight to see a shifting of paradigms, or an advantage to the supporting 
there IT customers. 
Personally, I like /FREE though I'm not allowed to use it in Production and see 
where it would be beneficial in the long run. 
If you've taught someone to fish and his method is sufficient to meet his 
needs, then that person will never use your new way unless it behooves them too.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Joe Pluta
Sent: Tuesday, May 18, 2004 7:38 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Compile error when using field in a subfield data structure


> From: Colin Williams
> 
> Lack of MOVE in free-format wouldn't bother me so much,
> if the need to put /free,/end-free, to switch from free to fixed and
back
> was removed.
> 
> Surely the presence of the spec, eg C,D,F etc on the left is enough to
> indicate that it's a fixed format line.

I agree.  This restriction is entirely unnecessary.  And Hans has stated
in the past that the restriction was put in place precisely to make it
difficult to switch back and forth.



> And although the MOVE opcode is powerful, its very power may be the
cause
> of
> many bugs over the years,
> as it packs a heck of a lot of functionality in one opcode, tthat you
can
> easily get wrong.

I disagree here.  This is simply a variation on the "programmers are too
stupid" argument.  There would be a lot fewer database problems if we
just got rid of that pesky UPDATE opcode, too <grin>.

Seriously, if you can't handle the MOVE opcode, you shouldn't be
programming.  You certainly shouldn't have pointers and based variables!


> As with all things in this game, its swings and roundabouts!

This I can agree with, anyway.  It's a business decision, not a
religious decision.  Fixed format RPG IV is just as powerful as free
format RPG, except where the RPG team has chosen to artificially
differentiate the syntaxes.

Joe

_______________________________________________
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.