Re: [Mingw-users] acceptable sources other than MSDN -- winehq/...wincrypt.h?

[amores p. <lif...@ho...>]

> Date: Sat, 03 Nov 2007 18:35:00 +0000
> From: Greg Chicares=20
> Subject: Re: [Mingw-users] acceptable sources other than MSDN -- winehq/.=
..wincrypt.h?
>

I wrote:

>> I don't see X509_ANY_STRING in MSDN online.
>

Greg wrote:

> I think its value is disclosed on msdn, in terms of another
> macro whose numeric value is specified:
>
> http://msdn2.microsoft.com/en-us/library/aa378145.aspx
> |
> | X509_NAME_VALUE
> | (LPCSTR) 6
> ...
> | X509_ANY_STRING
> | X509_NAME_VALUE
>
> So IMO it's acceptable to write
>
> #define X509_NAME_VALUE (LPCSTR) 6
> #define X509_ANY_STRING X509_NAME_VALUE
>


I am not sure I buy this. Those two (X509_ANY_STRING=20
& X509_NAME_VALUE) are written together as producing
the same data in the pointer, but I am not sure that
is a strong enough statement to mean they're actually
the same constants. I'd prefer to leave it undefined,
so that if someone runs into needing it, they can deal
with the issue then, as they may be in a good position
to test -- I would prefer not to define them as equal,
because I am not sure that that is true. So I'm thinking
along the lines of: better no definition than one that
might be wrong.


_________________________________________________________________
Help yourself to FREE treats served up daily at the Messenger Caf=E9. Stop =
by today.
http://www.cafemessenger.com/info/info_sweetstuff2.html?ocid=3DTXT_TAGLM_Oc=
tWLtagline=