Re: cvs commit: openssl/ssl kssl.c

2000-12-03 Thread Ben Laurie
[EMAIL PROTECTED] wrote: ben 03-Dec-2000 11:04:23 Modified:apps ca.c openssl.c ssl kssl.c Log: Fix warnings. Revision ChangesPath 1.71 +4 -4 openssl/apps/ca.c 1.32 +2 -2 openssl/apps/openssl.c Index: ca.c

Re: cvs commit: openssl/ssl kssl.c

2000-12-03 Thread Geoff Thorpe
Hi there, On Sun, 3 Dec 2000, Ben Laurie wrote: -static IMPLEMENT_LHASH_HASH_FN(index_serial_hash,const char **); -static IMPLEMENT_LHASH_COMP_FN(index_serial_cmp,const char **); -static IMPLEMENT_LHASH_HASH_FN(index_name_hash,const char **); -static

Re: cvs commit: openssl/ssl kssl.c

2000-12-03 Thread rsalz
Couldn't find a way to not get warnings and still have a semicolon, I'm afraid. Really? Weird ... is the compiler/OS running punched cards? grin it's hardly a biggee. I'm curious though why it doesn't accept them though - the macro expands into a function declaration so the trailing

Re: cvs commit: openssl/ssl kssl.c

2000-12-03 Thread Ben Laurie
Geoff Thorpe wrote: Hi there, On Sun, 3 Dec 2000, Ben Laurie wrote: -static IMPLEMENT_LHASH_HASH_FN(index_serial_hash,const char **); -static IMPLEMENT_LHASH_COMP_FN(index_serial_cmp,const char **); -static IMPLEMENT_LHASH_HASH_FN(index_name_hash,const char **);

Re: cvs commit: openssl/ssl kssl.c

2000-12-03 Thread Geoff Thorpe
Hey there, On Sun, 3 Dec 2000 [EMAIL PROTECTED] wrote: ; gcc -c -ansi -pedantic a.c a.c:3: warning: ANSI C does not allow extra `;' outside of a function :-) OK, I'm busted. hehe. Fair enough, I guess ANSI is as good a reason as any! I'll remove any other trailing semi-colons in the next

Re: cvs commit: openssl/ssl kssl.c

2000-12-03 Thread Geoff Thorpe
Hey there, On Sun, 3 Dec 2000, Ben Laurie wrote: is equivalent to whether you can follow a function's closing brace with a semi-colon. Which you can't in ANSI C. Yup, ok. :-) Another option would be using "inline" I guess, but I don't know how effective that is. Feedback welcome.

Re: cvs commit: openssl/ssl kssl.c

2000-12-03 Thread Dr S N Henson
Geoff Thorpe wrote: Hey there, On Sun, 3 Dec 2000 [EMAIL PROTECTED] wrote: ; gcc -c -ansi -pedantic a.c a.c:3: warning: ANSI C does not allow extra `;' outside of a function :-) OK, I'm busted. hehe. Fair enough, I guess ANSI is as good a reason as any! I'll remove any other

[STATUS] OpenSSL (Sun 3-Dec-2000)

2000-12-03 Thread OpenSSL Project
OpenSSL STATUS Last modified at __ $Date: 2000/11/19 14:11:03 $ DEVELOPMENT STATE o OpenSSL 0.9.7: Under development... o OpenSSL 0.9.6: Released on September 24th, 2000 o OpenSSL 0.9.5a: Released on April

Re: cvs commit: openssl/ssl kssl.c

2000-12-03 Thread Geoff Thorpe
Hey there, On Sun, 3 Dec 2000, Dr S N Henson wrote: I think the DECLARE and IMPLEMENT macros for most things don't have a semicolon anyway so it would be an idea to follow that for consistency. If you really want the semicolon then I suppose you could just include a superfluous prototype

I suggest functions' prototype defined as dllexport

2000-12-03 Thread SCH
If we define a function "BIGNUM *BN_new(void)" as " #define OPENSSL_FUNC __declspec( dllimport ) OPENSSL_FUNC BIGNUM* BN_new(void) " I think it is helpful when there are some reason for the users have to change to other OPENSSL_FUNC definition, at least it is helpful for me to

No Subject

2000-12-03 Thread Alex Cosic
Title: Hi, My question is on how to connect JSSE (java based client) with openssl based web engine server. I have tried so far and what I have got is that I could not create SSL socket with my opensl server, which works fine with my openssl client (even when I used JNI approach to use