|
I have two comments: 1) Shouldn't it be ExtProc('itoa') without the "_"? 2) Why not just use %EditC, %EditW or %Char? That's almost certain to be easier for the next guy to figure out... On Wed, 5 Dec 2001, Jim Langston wrote: > This is getting frustrating. > > Now I have my _itoa function declared right, but I'm getting linking error. > What's wrong with this, please? > > H DftActGrp(*No) > H BndDir('QC2LE') > > D itoa PR ExtProc('_itoa') > D 10U 0 > D * > D 10U 0 > > Getting linking error in the job log after successful compile. > > I've also tried ExtProc('itoa') > > >From module . . . . . . . . : QBNBSYMR > > >From procedure . . . . . . : QBNBSYMR__UnresolvedReferenceIterator > > Statement . . . . . . . . . : 31 > > To module . . . . . . . . . : QBNBSYMR > > To procedure . . . . . . . : QBNBSYMR__SignalUnresolvedReferences > > Statement . . . . . . . . . : 8 > > Message . . . . : Definition not found for symbol '_itoa'. > > Cause . . . . . : No definition was found for reference _itoa in *MODULE > > object MONIPGDMPS in library QTEMP. The definition either does not exist > or > is not of the same data or procedure type as the reference. Recovery . . > . > : Try the Create Program (CRTPGM) command again, supplying an object > that > contains a definition for symbol _itoa. > > > Regards, > > Jim Langston > _______________________________________________ > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list > To post a message email: RPG400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > 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 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.