Re: [AOLSERVER] Exposing API's to other modules?

2002-01-03 Thread Jim Davidson
In a message dated 12/28/01 12:02:35 AM, [EMAIL PROTECTED] writes: >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.

Re: [AOLSERVER] Exposing API's to other modules?

2002-01-03 Thread Scott Goodwin
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 anywher

Re: [AOLSERVER] Exposing API's to other modules?

2002-01-03 Thread Jerry Asher
>Is this a big deal? Changing function names just to be consistent may be >viewed as a waste of time. I don't happen to think so. It helps when I go >read another module's sources if they follow a style consistent with the >core stuff. I'm probably outnumbered in this view. I have worked on sever

Re: [AOLSERVER] Exposing API's to other modules?

2002-01-03 Thread Brett Schwarz
> 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? http://tcl.

Re: [AOLSERVER] Exposing API's to other modules?

2002-01-03 Thread Dossy
On 2002.01.03, Jerry Asher <[EMAIL PROTECTED]> wrote: > 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 t

Re: [AOLSERVER] Exposing API's to other modules?

2002-01-03 Thread Scott Goodwin
I believe nsopenssl conforms to these standards as they are written now. The standard you pointed us to covers function naming standards, but makes no distinction between functions in the AOLserver core versus functions in a module. /s. > On 2002.01.03, Jerry Asher <[EMAIL PROTECTED]> wrote: >

[AOLSERVER] unresolved external _h_errno?

2002-01-03 Thread Ramin Naimi
I'm trying to compile the source under SunOS (sparc) and I get the following error where in dns.c the _h_errno has been referenced and not resolved by link time. Does anyone know what I need to do to make the source compile under SunOS? This is what is printed (after second attempt to link): (c

Re: [AOLSERVER] unresolved external _h_errno?

2002-01-03 Thread Rob Mayoff
+-- On Jan 3, Ramin Naimi said: > I'm trying to compile the source under SunOS (sparc) and I get the following > error where in dns.c the _h_errno has been referenced and not resolved by > link time. Does anyone know what I need to do to make the source compile > under SunOS? I don't know

Re: [AOLSERVER] Exposing API's to other modules?

2002-01-03 Thread Jerry Asher
At 11:12 AM 1/3/2002, you wrote: >I believe nsopenssl conforms to these standards as they are written now. >The standard you pointed us to covers function naming standards, but makes >no distinction between functions in the AOLserver core versus functions in >a module. > > >/s. Hi Scott, I didn't