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

yes, I had the hex dump at the end of the compile listing also. Interesting!

-----Original Message-----
From: James H H Lampert [mailto:jamesl@xxxxxxxxxxx]
Sent: Friday, February 20, 2004 1:40 PM
To: mi400@xxxxxxxxxxxx
Subject: RE: [MI400] OK I give up - can't compile this MI source

> THANK YOU, THANK YOU, I didn't know about the colon requirement.

Yes, that was the first thing I noticed, too. The technical term is
"relative branch target." Without a colon, the compiler can't digest a
relative branch. (Pun intended.)

Usually when I leave one out, QPRCRTPG crashes, and puts many, many pages
of hex-dump at the end of the compilation listing. Once in a great while,
something will compile fine with a missing relative branch target, which
is kind of scary.

Nothing like wasting a 20-minute compilation of a 24,000-line source
member, because of a typo in one line.

Personally, I'm surprised it accepted such long identifiers. I don't use
any longer than about 8-10 characters.


This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mi400
or email: MI400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2023 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.