[openssl.org #1987] Definition of STRING conflicts with ntsecapi.h

2009-07-20 Thread Charlie Savage via RT
From safestack.h, line 113, in 1.0 beta 3: typedef char *STRING; typedef const char *CSTRING; Using such generic names seems like a really bad idea - its asking for conflicts. And they do happen, at least on windows. The problem is that one of the windows headers, ntsecapi.h around line 134

[openssl.org #1987] Definition of STRING conflicts with ntsecapi.h

2009-07-27 Thread Stephen Henson via RT
> [c...@savagexi.com - Mon Jul 20 11:01:32 2009]: > > > I assume other programs that use openssl and ntsecapi will also fail > to > compile. Any chance these generic typedefs can be changed to > something > like OPENSSL_STRING and OPENSSL_CSTRING? This has been changed to OPENSSL_STRING etc. Pl