|
Hello Booth (and David), Well COBOL has it's own list, although it's VERY quiet (Is that because COBOL programmers are _better_ than RPG programmers and don't have to ask so many questions? Or just 'cause no-one uses it? Tongue firmly in cheek!). I'd think programming languages are sufficiently different to warrant separate coverage -- hence the Java, MI, and COBOL lists. REXX should also have a separate list if there is enough activity. Perhaps the ideal is a PROGRAMMING list for the CL, DDS, possibly REXX, OPNQRYF, SQL and other general programming issues thus leaving MIDRANGE-L for the topics you suggest. Even when those techniques are being used in an RPG application they are rarely related to specific RPG issues. A general programming list could be used to argue the DOU/DOW issue (but not if I'm the moderator** -- and you can take that as me volunteering for the job) and other language-independant issues. What say you all? Should we separate the topics or alter the function (and name) of the RPG400 list? I can see Midrange Dot Com taking over from the trade rags ... pity about the NASDAQ ... the IPO for Midrange Dot Com would have been interesting :) ** A read loop should almost always be a DOW. The issue being currently argued is really whether a priming read should be used or a single read in an IF test inside the DO. I used to be in the IF camp when I first started programming but after a while I started thinking about the construction of the loop and the additional unnecessary IF test and changed to the priming read. I know there is nothing worse than a reformed convert but those still in the DOU or extra IF camp are simply wrong. You can mask that with arguments about religion, style, or "it's always worked for me" but the fact is it's wrong. No amount of persuasion from either side will create a convert. You have to THINK it through for yourself. ITER and LEAVE (and the appalling LEAVESR) fall in to the same category and I've said enough about them in the past. Regards, Simon Coulter. «»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«» «» FlyByNight Software AS/400 Technical Specialists «» «» Eclipse the competition - run your business on an IBM AS/400. «» «» «» «» Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 «» «» Fax: +61 3 9419 0175 mailto: shc@flybynight.com.au «» «» «» «» Windoze should not be open at Warp speed. «» «»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«» //--- forwarded letter ------------------------------------------------------- > X-Mailer: Lotus Notes Release 5.0a May 4, 1999 > Date: Sun, 16 Apr 2000 16:07:06 +0000 > From: boothm@earth.Goddard.edu > To: RPG400-L@midrange.com > Reply-To: RPG400-L@midrange.com > Cc: none > Subject: Seeing a file on the IFS in V3R7 > > No. its probably a matter of misunderstanding on my part. I tend to think > of the Midrange List as being more for the operations and management > aspects of the AS/400. For instance, I'd think that list was the place > for comments and questions about IBM marketing & advertising, security, > policy, model characteristics, management and training, connectivity, the > internet and software packages. > > I think of the RPG list as being more for language and database questions. > For instance I would consider this the right list for questions and > comments about CL, COBOL, DDS, FMTSRC, and REXX, but not Java or > Code/400. > > _______________________ > Booth Martin > boothm@earth.goddard.edu > http://www.spy.net/~booth > _______________________ +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.