× 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.



Don't get me started on *INZSR...

A secret hidden little beast somewhere in the code that runs on its' own.... <grin>

Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power

 
 





From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxx> on behalf of John Yeung <gallium.arsenide@xxxxxxxxx>
Sent: Tuesday, August 1, 2017 8:38 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: This is cool.
 
On Tue, Aug 1, 2017 at 10:36 AM, Mark Murphy/STAR BASE Consulting Inc.
<mmurphy@xxxxxxxxxxxxxxx> wrote:
I don't know how this is wallowing in the past.

Not that this was your point, but I would like to remind people that
newer isn't *always* better. We should be thinking critically, instead
of using chronological age as a proxy for quality (or lack thereof).

It all seems a bit arbitrary to me. Particularly since [various methods of initialization] all seem equally valid in my mind.

Indeed. In addition to what you mentioned, it's also perfectly
reasonable to want your *type declarations* separate from any
*assignment of data*. Even if that assignment is at initialization
time. And, all else being equal, I can totally see how it might be
nice to have all your initializations in one place, rather than some
at the top (in D specs) and some at the bottom.

(I'm not advocating that we now do ALL our initializations in *INZSR.
Just adding to Mark's theme of "there are multiple reasonable ways" to
do things.)

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.