>> * Scott Williams <begzntr@...> [2005-11-29 12:27:15 -0700]:
>> What's the best way to get computed DEF-CALL-OUTs?
Sam's proposition is ok, but what is realy dynamic in your requirements?
o Do you really need names for the functions, instead of function objects?
o Isn't it more like a lazy declaration (on a by-need basis)?
o Is a shared ilbrary involved?
What I mean is that if you intend to call functions from a shared library, there's a fixed and known set of functions, and people usually write large files of def-call-out forms.
Now, if OTOH you don't have functions located in some library, but dynamically created function addresses, you can call these (e.g. consider the foreign-function constructor) without having to defined a name.
Some people (including myself) tend to object to large lists of (mostly unused) def-call-out forms. Is that what you're trying to avoid by creating the functions only when actually referenced?
Or do you really create a possibly unlimited number of functions at run-time (e.g. what COM/DCOM would presumably want to do)?
Would you like to be more specific about your needs?
Get latest updates about Open Source Projects, Conferences and News.