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



> From: Fisher, Don
> 
> These procedures are all in the same module.  I thought about making
the
> data structures global, but I really want each of the four "main"
> procedures
> to have independent copies of the data.  I could, of course, define
four
> global data structures with the PREFIX keyword, but I think the
> EXPORT/IMPORT approach is more elegant.  It has the added benefit of
> showing
> the relationship between the "main" and "child" procedures.

I don't think EXPORT/IMPORT will do what you want it to do.  Back in the
bad old days, we called these "external references", and what they in
fact do is point all the IMPORTed references to the one EXPORTed
variable.  In effect, they all shard the same address.  So if ProcA
updates the IMPORTed variable, ProcB will see the change (as will ProcC,
ProcD and the main procedure).

I guess I don't understand what you're trying to do.  Typically, I TRY
to get all my procedures to share a common buffer where practical.  I
can't quite get my brain around why you want multiple copies of the
data.

Joe


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.