> If IA5STRING used a typedef instead of a #define, then this wouldn't be
> a problem (and it'd be properly typesafe), would it?
To pick a nit: it would probably work. It would not be more typesafe,
since typedef does NOT introduce a new type, just a new name.
typedef int T1;
typedef int T2;
static void nullit(T1* t)
{
*t = 0;
}
int main(int ac, char **av)
{
T1 t1 = 1;
T2 t2 = 2;
int i = 3;
nullit(&t1);
nullit(&t2);
nullit(&i);
return 0;
}
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
- DECLARE_STACK_OF(ASN1_UTF8STRING) and 0.9.4 problem. Jean-Marc Desperrier
- Re: DECLARE_STACK_OF(ASN1_UTF8STRING) and 0.9.4 ... Ben Laurie
- Re: DECLARE_STACK_OF(ASN1_UTF8STRING) and 0.9.4 ... Dr Stephen Henson
- Re: DECLARE_STACK_OF(ASN1_UTF8STRING) and 0.9.4 ... Dr Stephen Henson
- Re: DECLARE_STACK_OF(ASN1_UTF8STRING) and 0.... Jean-Marc Desperrier
- Re: DECLARE_STACK_OF(ASN1_UTF8STRING) and 0.... Ben Laurie
- Re: DECLARE_STACK_OF(ASN1_UTF8STRING) an... Dr Stephen Henson
- Rich Salz
