|
jt, No one will be able to change your opinion about the beauty of fixed form. Where you get it takes seven times longer to learn over free is beyond me. Please quote the study that provided that figure. Which is easier to understand: /free if a>b; ... /end-free or C A COMP B 75 C 75 EXSR DOIT Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "jt" <jt@xxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 11/19/2003 08:47 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx> cc Subject RE: RPG IV release levels and complexity | -----Original Message----- | From: rpg400-l-bounces+jt=ee.net@xxxxxxxxxxxx | [mailto:rpg400-l-bounces+jt=ee.net@xxxxxxxxxxxx]On Behalf Of Bob cozzi | Sent: Tuesday, November 18, 2003 12:11 PM | To: 'RPG programming on the AS400 / iSeries' | Subject: RE: RPG IV release levels and complexity | | | Hi Scott, | | Here's a posting from another list that typifies why /FREE can be ugly (as | can fixed-format). If this is more "readable" I need my glasses. Granted | this is just one example and the embedded SQL in RPG is ugly in | general (not | as bad as it is in other languages). | | =================== | | /free | myHostVariable = 'Select * from myLib/myFile' ; | /end-free | c/exec sql | c+ declare myCursor Cursor | c+ for myPreparedStatement | c/end-exec | c/exec sql | c+ prepare myPreparedStatement | c+ from :myHostVariable | c/end-exec | c/exec sql | c+ open myCursor | c/end-exec | c/exec sql | c+ fetch next from myCursor into :masterDS | c/end-exec | /free | dow sqlStt <> '00000' ; | // do stuff | /end-free | c/exec sql | c+ fetch next from myCursor into :masterDS | c/end-exec | /free | enddo ; | /end-free | c/exec sql | c+ close myCursor | c/end-exec | =================== | | | Bob Cozzi | Cozzi Consulting | www.rpgiv.com | | | -----Original Message----- | From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] | On Behalf Of Scott Klement | Sent: Tuesday, November 18, 2003 10:48 AM | To: RPG programming on the AS400 / iSeries | Subject: Re: RPG IV release levels and complexity | | | > So, I'd have to say that we haven't experienced the type of problems you | > have described. In fact, I'm all for making enhancements to | the language. | > (What I don't want to see are enhancements that are only | available if you | > use /free. I don't see enough return on investment to make the leap to | /free | > yet and I resent seeing good language enhancements that we would use but | > can't because of the time involved in retraining 20 programmers for | minimal | > gain). | | | There are two things that /FREE buys you. | | 1) Extra space on each record for your statements. (This has made a | HUUUUGE difference in readability for me) | 2) The ability to indent your statements. | | As there is absolutely no "investment" that I can see, I don't see why | you're worried about it. It takes what, 20 minutes to learn? | | I haven't seen any new features that only work in /FREE. Have there been | any? Well, Scott. It takes about 3 minutes to understand a fixed-form calc statement, but I don't see many trying to make even THAT much effort lately. Wonder why?? Mebbe it has to do with most-ALL enhancements going to EVAL, and /free? Even though it takes 7 times longer to learn. Hm? :-\ ? _______________________________________________ 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.