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



When the API doc says to pass a character pointer, all you need to do in CL is pass a variable normally - all parameters are passed by reference, therefore they are pointers already.

Make sense?

Vern

At 08:50 AM 9/27/2005, you wrote:

Thanks Barbara.

Do you mind explain why it wouldn't work when parm is defined to pass by value? 1. The doc only say to pass by char pointer. In my CLLE program I pass the variable &BBCD by reference, which match what the doc ask for.

My guess is that because it is define to pass by value, the caller is resposible to move the value of the passing parm to the parm memory address in the procedure. Since CL doesn't know to do that, it wouldn't work.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Barbara Morris
Sent: Monday, September 26, 2005 6:23 PM
<clip>
The only types that are valid to be passed by value using QZRUCLSP are
4-byte integer and pointer.
  - 10i 0
  -   *

Any other types have to be passed by reference.  So it's impossible to
call this procedure using QZRUCLSP.  If you need the procedure in this
form, you could create a wrapper that has the piBBCD parameter passed by
reference, and have it call through to this procedure.

Under "Parameter Formats" in the API doc:
  Each array entry should be one of the following:
    1   The parameter is a BINARY(4) argument to be passed to the
procedure by value.
    2   The parameter is a pointer value.
</clip>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.