> There was suggestion to fall back to wfopen from a vmware engineer a while > ago, but he couldn't provide patch (not that it would be very complex) and > it was not followed up. Idea must have been something similar to just > committed http://cvs.openssl.org/chngview?cn=19610.
Sounds like a good idea, but perhaps an even better idea would be to provide an alternate BIO_new_file() that takes a wchar_t*. It would call _wfopen() if supported by the compiler, and if not it would convert the wchar_t* to a char* using wcstombs() and call fopen(). > Please note that it's *not* like I disapprove practice of custom BIO and > suggest you to abandon it. It's *not* like that. On the contrary I can > appreciate advantage and even say that it's better approach than one > suggested in the beginning of the thread. A. Cool, thanks :) Yeah, I was quite happy with myself that I happened to write a custom BIO just in time to avoid the whole applink mess, even though that's not even the reason I wrote it. Phillip ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
