×
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.
Loyd,
I completely agree. I wonder if you missed my point. My point is, "why is 'Not' hard to read/understand/parse?" It seems like the preference boils down to 'different people read code in different ways' (it's the environmental impact of our programmer upbringing?).
-Kurt Anderson
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Loyd Goodbar
Sent: Monday, March 01, 2010 2:48 PM
To: RPG programming on the IBM i / System i
Subject: Re: More on RPG style
It seems to me in that case:
if not %eof(somefile);
is easier and quicker for a person to parse than:
if %eof(somefile) = *off;
The first case it is immediately clear we expect a negative outcome of the
condition (something didn't happen). The second case evaluates a positive
condition (something equals something); we have to read the entire condition
to determine its outcome.
Was it Knuth who said that code should be written for people to understand,
and it just happens the machine executes it?
--Loyd
On Mon, Mar 1, 2010 at 10:46 AM, Kurt Anderson <kurt.anderson@xxxxxxxxxxxxxx
wrote:
Personal choice then, I guess. To me that seems excessive. You need to
create a D-spec for No.
I believe this is generally accepted as a coding technique:
If not %eof(fileName);
It's really no different.
-Kurt Anderson
midrange.com
