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



<snip>
Is there a difference between the CL processor and the command parser?
This always confuses me.
<snip>


Yes there is a difference....

In a CLP (program), the compiler can determine the attributes of data being
passed, and will not need to analyze the parameter data in order to declare
storage. There are no ambiguities in compiled CL.

In a command line scenario, you would most likely create a *CMD object to serve
as the parser. Again, because the CMD object is compiled, and the command
source fully defines the type and dimensions of the data elements, there is no
need to analyze the data to determine its type and length.

In the CALL command, when processed from the command line, you do not have
access to parameter sizing information, so the parameter data fields need to be
analyzed and an "appropriate" size for parameter data need to be determined.

Eric



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.