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



Converting *ENTRY & PLIST to free format.
Are there some simple examples, tutorials, and explanations on replacing *ENTRY? I am having trouble understanding the process.

I found this on Brian May's site:
http://www.bmeyers.net/faqs/15-faqs/51-replacing-entry-plist-with-a-prototype

I fear the example on Brian MEYER'S website is not correct. The EXTPGM keyword requires a parameter. Here are some simple examples that I have tested:
============================================
// Module/program name is ENTRYPARM1
// Compiler warning - external program name not same as program name

D EntryPlist Pr ExtPgm('RUBBISH')
D 10A Const

D EntryPlist Pi
D String 10A Const
============================================
// Module/program name is ENTRYPARM2
// No compiler warnings

D EntryPlist Pr ExtPgm('ENTRYPARM2')
D 10A Const

D EntryPlist Pi
D String 10A Const
============================================
// Module/program name is ENTRYPARM3
// Source will NOT compile - keyword EXTPGM requires a parameter

D EntryParm3 Pr ExtPgm
D 10A Const

D EntryParm3 Pi
D String 10A Const
============================================

As Brian Meyer correctly states:

o The prototype for the main procedure must include the EXTPGM keyword.
o The procedure interface must be named (the same as the prototype).
o The prototype must precede the procedure interface.

Hope this helps.
Brian Parkins.


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.