Re: Procedure pointers - can I do this??

["Peter Dow" <maillist@xxxxxxxxxxxxxxx>]

Hi Larry,

As someone pointed out somewhere on this list, one of the advantages of
getter/setter procedures is that they can determine what they're going to
return, and in fact, even if they're going to return something.  Why not
simply have the getter procedure check to see who the caller is?  If it's a
service program, allow it, otherwise, fail.  Presumably you could have any
other criteria you like to decide whether to return the value to the caller
or to send an escape message or something to have it fail.

Peter Dow
Dow Software Services, Inc.
909 793-9050 voice
909 793-4480 fax
951 522-3214 cell


> Here's the rub - to export the getter method I would flag it as EXPORTable
> and compile the module. I'd then explicitly export the getter method from
> the service program object using binder language. BUT this is now
available
> to ANY program that binds to the utility service program. There is no way
> (that I know of) that the utility service program can determine whether it
> should export or not.




---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.815 / Virus Database: 554 - Release Date: 12/22/2004