Re: Passing user data to password callbacks

[Richard Levitte - VMS Whacker]

3moeller> > Backward compatibility is an important issue.  Think "dynamic
3moeller> > library".
3moeller> 
3moeller> The funny thing here is that if we just add the parameters,
3moeller> then on systems with "standard" calling convention old
3moeller> programs should run without any problems with newly compiled
3moeller> shared libraries: The new library functions will expect one
3moeller> parameter that is not actually there and will take whatever
3moeller> happens to be on the stack and pass it to the callback
3moeller> function as a "pointer argument"; the callback function in 
3moeller> turn just ignores this extra (garbage) argument.

Yes, there is that special case, and it also assumes that the library
does nothing with the argument in question but pass it on.  I know,
that's more or less the case today, but...

(I'm into the "better safe than sorry" religion :-))

-- 
Richard Levitte   \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken  \ S-161 43  BROMMA  \ T: +46-8-26 52 47
                    \      SWEDEN       \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis             -- [EMAIL PROTECTED]

Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
Development Mailing List                       [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]