× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Last night whilst sipping my Manhattan on my deck (I find mint juleps far too
sweet) did I think about work?? Not in the slightest. :-)

But, on the subject of subfiles , I still find that a lot people, even for the
simplest of subfiles want to put in code to control the scrolling, and want to
build it page at a time even though they know it will NEVER be more than 2-3
pages long. Happily, for me, I have not had to build a subfile in years that
cannot be built all in one go and with the system handling everything, though I
have had to maintain a few of the others and what a pain it is. The standard
for my current shop is that if the subfile is over 999 lines long the program
will crash, that is the standard I didn't write it, so, for one of the few
times, on the programs I have changed I go against the standard and don't allow
the program to crash, hey maybe I am one of those Rogue(or is it Rouge)
Programmers that people are talking about. :-)

Steve

-----Oorspronkelijk bericht-----
Van: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]Namens Jerry Adams
Verzonden: vrijdag 27 april 2007 15:10
Aan: RPG programming on the AS400 / iSeries
Onderwerp: Re: Chalk one up for "The Cycle"


Last night, while sipping a mint julep on my deck, I got to thinking
about the "non-cycle is more logical, intuitive." I have to agree with
the statement, though I occasionally write cycle programs in ILE RPG
(even with subprocedures - how sick is that?).


But, then, I remembered subfile programs. Though I write subfile
programs, no one has (yet) been able to convince me that subfiles are
"easy and intuitive" to understand. On the other hand I wrote subfile
programs on the /36. Since the /36 doesn't have the built-in
(cycle-like?) subfile stuff, everything (and I mean everything) had to
be coded in the routines.


As much of a pain as subfiles are to program (or maybe it's just me), I
haven't heard (and don't expect to hear) anyone wanting to code subfiles
outside the built in system logic and handling. I no longer write
subfiles "manually;" that would be pretty masochistic.


* Jerry C. Adams
*IBM System i5/iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Mark Villa wrote:
I like the film industry analogy *much* better than the one I was
going to use, my spark plug wrench. Don't use it often but it's there
when needed and is the best tool for the job.

The cycle? Yes, just tell the newbies to think of it like "the
original 4GL" = some of the work is automated. They won't have to
crack a book.
And that the only problem with the language and utility is that MS did
not market it.

Putting SQL in production is more complex to QA IMHO. But when
considering multi-platform development it is obviously the preference
between these two.


It is when the rogue programmer _decides on their own_ to use something

different that they cause problems. <<

<<-- I bet this rarely happens in the real world. lol


Mark



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.