Re: weird compiler behaviour with procedures -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: weird compiler behaviour with procedures
From: James Rich <james@xxxxxxxxxxx>
Date: Tue, 28 Oct 2003 23:36:31 -0700 (MST)
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On Tue, 28 Oct 2003, Buck wrote:

> > The procedure I added appears before the
> > compile-time arrays (remember, this is old-school
> > code here).  The procedure I added does not
> > reference the record format in question, nor
> > does it reference the field WOSTAT.  But now
> > the compile fails!
>
> Did you also add 'h debug' perchance?

No, I didn't.  But test I did surround the procedure related code with :
/if defined (DEBUG)
...
/endif
so I could set a precompiler switch to enable the code.  Without DEBUG
defined it compiles, with it it doesn't.

James Rich

Follow-Ups:

Re: weird compiler behaviour with procedures , Buck

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