Greetings. > I'd like to see a mixture of high and low level features available in one > nicely done module than having features scattered across various > Win32::File* modules.
I forgot to highlight another point I've mentioned in my initial posting. My module would provide no low-level function and, cetrainly, no *A functions. I'm sick and tired of 95% software I see unable to handle Unicode properly and stumbling upon first filename with symbols outside current locale (and as Russian that have interest in Japanese and other Asian languages I encounter this situation pretty much every day). Even software that use tstr* and _T* macros often doesn't work with Unicode because authors just don't bother to select Unicode in MSVC compile options! Software that would use my module would be free from such problems from start. There just won't be any functions that let authors to work with anything but Unicode. Win32API::File, OTOH, have ASCII mode as default and even if you load *W functions you are still free to use *A counterparts. For me this is unacceptable. -- Oleg "Rowaa[SR13]" V. Volkov
