|
yes but you still end up with lots of /free /end-free even in SRs. The company I work for doesn't have WDSc & I'm sure that there are many more out there that do not use WDSc or any other GUI type IDE for RPG. Thanks, Tommy Holden -----Original Message----- From: Rick.Chevalier@xxxxxxxxxxxxxxx [mailto:Rick.Chevalier@xxxxxxxxxxxxxxx] Sent: Tuesday, October 26, 2004 9:04 AM To: rpg400-l@xxxxxxxxxxxx Subject: RE: RPGIV: RPGIII to get a facelift? For embedded SQL place the SQL code into subroutines. The calls can be from your /free code without going out and back in. I've been doing that for a year or so now and I prefer it because the basic logic flow isn't interrupted with the SQL compiler directives. To find the SQL code I just look for the subroutine. Real easy with WDSc outline view. Just me .02. Rick -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Holden Tommy Sent: Tuesday, October 26, 2004 8:24 AM To: 'RPG programming on the AS400 / iSeries' Subject: RE: RPGIV: RPGIII to get a facelift? I'm gonna add my /free pet peeve.... no support for embedded sql!!!! everytime I have to use embedded sql it's /free /end-free sql stuff /free /end-free... maybe just add this for free format: Exec SQL; Select MyStuff Into MyDS From MyFile; End-Exec; come on IBM please give us a fix!!! (FWIW I love free-format....but I prefer a finished version =0) Thanks, Tommy Holden -----Original Message----- From: Colin Williams [mailto:colin.williams@xxxxxxxxxxxx] Sent: Tuesday, October 26, 2004 2:52 AM To: 'RPG programming on the AS400 / iSeries' Subject: RE: RPGIV: RPGIII to get a facelift? Reeve It's the Programming Police. Your right, they should move everything over to /FREE and get rid of the /FREE, /ENDFREE tags. To get over the lack of goto's for display file processing, I use the FOR Eg: FOR I = 1 to 1 if x = true leave endif ENDFOR Works fine! cheers Colin.W Extension 5800 Direct dial 0870 429 5800 -----Original Message----- From: Reeve [mailto:rfritchman@xxxxxxxxx] Sent: 26 October 2004 08:15 To: rpgiv@xxxxxxxxxxxxxxx Cc: RPG programming on the AS400 / iSeries Subject: Re: RPGIV: RPGIII to get a facelift? I think IBM should focus 100% of their efforts on completing /FREE. Until RPG is a completely free-form language, it's incomplete and it does nothing to bring new recruits into the fold. I've talked with several "older" programmers who feel no need to move to /FREE because H, F, D, and O specs are still fixed-format. Younger programmers just turn their nose up at the current neither-fish-nor-fowl /FREE implementation. Seeing a moderately contemporary progam littered with /END-FREE and /FREE is more than moderately annoying. I can use my service program library to handle MOVE issues (and others) but the lack of a free-form GOTO/TAG is a burr under my coding saddle. My standard structure for handling a rich mixture of command keys, help panels, and lookups is not well-suited for the glib suggestion in the Reference manual to "use other operation codes, such as LEAVE, LEAVESR, ITER, and RETURN" instead of GOTO. Is there a technical reason GOTO and TAG can't be free-formed? Or is this the Programming Police in action, telling us a complex set of nested loops for flow control promotes program readability? I'm thinking about my customers' junior programmers trying to make sense out of Nested Loop Soup. Like most of us, I spent a lot of time in non-/FREE code, and I'd like to convert it to /FREE without rewriting it. It's well-structured code (not spaghetti); then I use CODE (i.e. leave WDSC, hop into CODE) to convert it, and it gets ugly with /END-FREE and /FREE from dealing with the unsupported op codes. We have a tool, /FREE, to cut through layers of to-do lists. It would be a better tool if it were sharper, and charging for the rusty blades of old, less efficient tools doesn't serve any purpose other than to annoy the small number of customers requiring the facility for program maintenance. -reeve On Mon, 25 Oct 2004 15:22:28 -0500, Bob Cozzi <cozzi@xxxxxxxxx> wrote: > > I spent one day at COMMON last week and talked with several of the IBM > Canada RPG IV developers. One of the questions that was asked was if > IBM could/should start charging for the RPGII and RPGIII compilers > (some people call RPGIII, "RPG400"). > > Anyway, I suggested that IBM should enhance RPG IV with two new > features: > > 1) Allow blank lines in the source code > 2) Support the compiler parameters in the H spec, and translate those > parms when the CVTRPGSRC command is used. > > Without leading your responses: I'm wondering if you feel charging for > RPGIII would help/encourage you to move to RPGIV more aggressively? > > -Bob > > ------------------------ Yahoo! Groups Sponsor > --------------------~--> $9.95 domain names from Yahoo!. Register > anything. http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/saFolB/TM > --------------------------------------------------------------------~- > > > > www.RPGxTools.com > "Free your Limitations" > Now with CGILIB - The best CGI RPG library available. > > To unsubscribe from this list send and email to: > rpgiv-unsubscribe@xxxxxxxxxxxxxxx > > Yahoo! Groups Links > > <*> To visit your group on the web, go to: > http://groups.yahoo.com/group/RPGIV/ > > <*> To unsubscribe from this group, send an email to: > RPGIV-unsubscribe@xxxxxxxxxxxxxxx > > <*> Your use of Yahoo! Groups is subject to: > http://docs.yahoo.com/info/terms/ > > -- 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. This e-mail has been sent by a company of Bertram Group Ltd, whose registered office is 1 Broadland Business Park, Norwich, NR7 0WF. This message, and any attachments, are intended solely for the addressee and may contain privileged or confidential information. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. If you believe that you have received this email in error, please contact the sender immediately. Opinions, conclusions and statements of intent in this e-mail are those of the sender and will not bind a Bertram Group Ltd company unless confirmed in writing by a director independently of this message. Although we have taken steps to ensure that this email and any attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. -- 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. -- 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. -- 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.