|
Joep, Yes, we do some new programming; it's not all maintenance. And I do intend to push towards RPG IV (albeit gently). For example, I have already written about 6 short no-brainer programs that the other guy in the shop could modify with no problem if I weren't around to explain the different syntax. What I'm waiting for is an opportunity to spring some RPG IV functionality on my boss that's not present in RPG III. The concept of local/global variables might sway him in the future. Right now, if I could numeric edit a character field (with numeric data, obviously) on a printer file O spec, that may do the trick. All in all, it will have to be a gradual change; we all are afraid of what we don't understand. Thanks for listening and any offers of whiz-bang code snippets would be greatly appreciated! Buzz Fenner bfennerNS@jonesborocwl.org Remove NS to reply P.S. Your code is perfect? I thought I was the only one who did that. -----Original Message----- From: Joep Beckeringh [SMTP:joepb@tip.nl] Sent: Thursday, August 19, 1999 3:44 PM To: RPG400-L@midrange.com Subject: Re: More on Call or Bound Call Buzz, Does your boss ever ask you to write something new? If so (of course he does), it's easy: 'Ah, I'm afraid that is technically impossible/would cost me two weeks in RPG III. Now if I could use RPG IV ...' As for my code not being 'critiqued': why should it be? It is perfect! (Although some of my colleagues get to read it and sometimes have very annoying questions). Joep Beckeringh ----- Oorspronkelijk bericht ----- Van: Buzz Fenner <bfenner@jonesborocwl.org> Aan: Discussion RPG (E-mail) <RPG400-L@midrange.com> Verzonden: donderdag 19 augustus 1999 17:10 Onderwerp: More on Call or Bound Call > I appreciate all of the feedback from Joel, Jon, Scott, Joep, and David > (hope I didn't forget anyone). I have two goals in putting these types of > posts on the discussion group. One, as you may guess from the subject > matter of my original post, is to gather useful information pertaining to > performance advantages of RPG IV over RPG III. Second, will be to find > opcodes, bif's, etc., that provide added functionality over what my shop > has now using RPG III. However, I have to sell my boss on making a move > towards RPG IV, and he will be a hard sell coming from the "If it ain't > broke...," point of view. Plus, I'm in a Catch 22 situation: How do I > learn without writing new code vs. the mind set of not changing the status > quo. (I realize I'm flogging a dead horse here, and I'm getting away from > the subject at hand). So, I'm gathering ammunition and hopefully will > choose my battles wisely. > > Also, I take no offense with any criticism of my syntax. After all, if > other people (with you guys being the experts) don't see what you do, it > never gets critiqued! > > Buzz Fenner > bfennerNS@jonesborocwl.org > Remove NS to reply > > +--- > | 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 > +--- > +--- | 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 +--- +--- | 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-2025 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.