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



Jon,

I have many programs with lots of internal subprocedures with only a
dcl-pi definition, but so far I have had no problems with the outline. I
just took an RPGLE member with internal subprocedures with PR and PI
definitions; removed all the PR definitions; no problem. Exited LPEX,
reloaded, still no problem.

Joep Beckeringh
systeemontwerper
Pantheon Automatisering B.V.
Heerenveen

info@xxxxxxxxxxxxxxxxxxxxxxxxxx
www.pantheon-automatisering.nl
KvK 01055135


Jon Paris <jon.paris@xxxxxxxxxxxxxx>

19-05-2016 00:17

[WDSCI-L] Error in Outline view processing?

Before I go to the trouble of opening a PMR can someone else please
confirm this for me to make sure it is not just me.

It seems that when the compiler rules re Prototypes were changed,
the code that builds the Outline view was not updated.

If I have an internal subprocedure with only a PI definition then it
simply doesn’t appear in the outline view at all. In my case this
particular subproc was used as the handler for XML-SAX so I thought
that might be the cause - but I have since checked with another
ordinary subproc and the result ins the same.

Interestingly the same outline view has also “lost” at least one
stand-alone field. It just isn’t there despite being used in a
number of places.

P.S. The code compiles just fine.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.