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



Surprising that the compiler would let it through. %Error is a function and
all functions have to have a parenthesis so surprised they do not require
it.

On Fri, Apr 23, 2010 at 1:44 PM, Dennis Lovelady <iseries@xxxxxxxxxxxx>wrote:

I mistakenly coded %Error() (with parenthesis) rather than just %Error.
I
was surprised when there was no compile error. I checked the RPG
manual and
%Error() was not found. I also checked the list archives but couldn't
find
this specific question.

%ERROR is the only BIF I can think of that has no parameters. My thinking
has always been that the syntax checker allows () on any %BIF whether
they're needed or not. I usually (almost always) code this as %Error().
(I
don't if I'm working on a program/module where it's already coded without.)
But maybe that's not so good.

I'm very curious to see what others might have to say on this.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Our vision is to speed up time, eventually eliminating it."
-- Alex Schure

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



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.