Well, the cat's out of the bag already. Let's set a standard for exposed
functions that sit within modules.
Currently, in nsopenssl's case:
NsOpenSSL* functions are externed but are not to be called from outside the
module.
Ns_OpenSSL* functions are external APIs that can be called from
One of Ousterhout's greater contributions was the documentation of his
team's programming standards. I apologize for ending this message
without
the link. But if they're not there already, maybe the AOLserver.com
folks
could link to them from their site.
maybe this link?
Hello,
How can a module X expose API's to other modules?
I can think of the following possiblities:
A) Add Tcl commands, so the other modules could execute the commands
B) Register for URL(s), maybe one URL with parameters for which function and
the function parameters encoded in the URL, or
+-- On Dec 27, Ramin Naimi said:
Hello,
How can a module X expose API's to other modules?
Hmm. I thought a module could refer to another module's exported C
functions directly. Have you tried it?
For C modules, simply create the C functions you want exposed from your
module as externs and call them Ns_SomeName. Just make sure you don't
conflict with a C function name that already exists in the core or in other
modules. You do this by prepending something that you think is going to be
