RE: RPG IV release levels and complexity

["Bob cozzi" <cozzi@xxxxxxxxx>]

Scott,
Maybe IBM should drop support for the READ/WRITE/OPEN/CLOSE/UPDATE opcodes
so that we are forced to upgrade and/or purchase SQL. <vbg>
What I meant by fixed-format can be ugly is that any code can be ugly, but
mixing SQL and /FREE is always ugly.

Bob Cozzi
Cozzi Consulting
www.rpgiv.com


-----Original Message-----
From: rpg400-l-bounces+cozzi=rpgiv.com@xxxxxxxxxxxx
[mailto:rpg400-l-bounces+cozzi=rpgiv.com@xxxxxxxxxxxx] On Behalf Of Scott
Klement
Sent: Tuesday, November 18, 2003 1:16 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: RPG IV release levels and complexity



On Tue, 18 Nov 2003, Bob cozzi wrote:
> Here's a posting from another list that typifies why /FREE can be ugly (as
> can fixed-format).

If both /free and fixed format are ugly (which is exactly what you've
said) then what good does it do to stay with fixed format?

My experience has been that things get ugly whenever you switch back and
forth between fixed-format and /free.   I try to never mix /free and fixed
in the same subprocedure.   If I *must* have fixed for some reason (which
I'm not sure I've even run into yet) I put it into it's own subprocedure.

Of course, I don't use SQL, which might be part of the reason I don't see
the disadvantage.

I should really learn SQL, it would probably make me a better programmer.
But, I haven't yet seen a need for it -- and the company I work for does
not own the licpgm...
_______________________________________________
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.