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



The LPEX editor used for editing RPG in WDSC 5 has code completion support 
like Java does.  For example, if you start typing a %BIF in an EVAL 
expression it will pop-up suggestions, as Java might for the methods on a 
class.

There is also a new Outline view (or rather they populate the existing 
Eclipse Outline view).  With RPG source open hit refresh on the outline 
view and it will pull in a list of all files, fields, indicators, 
subroutines, procedures etc. used in the code.  Clicking on an item takes 
you to that spot in the source code.

I had always noticed these two features, but not until today did I put 
them together.  If you have the outline view populated, then you get very 
nice code completion in the editor on everything.  Such as field name 
completions on an EVAL or file/format names on a CHAIN.  For fields, it 
even tells you the type and length. 

Very nice!

This all leads to a question.  Is there anything in the documentation that 
describes how to proactively use the cache that is used by the program 
verifier (and I presume the outline view).  For example, can I manually 
prime my cache with file descriptions so that I can use these cool 
features without incurring the overhead of resolving all of the references 
each time?  I have poked around and do not see it mentioned anywhere.

Thanks

Mark




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.