Denis Koroskin Wrote: > > LPCSTR currently resolves to char*/const(char)*, but it could be better > for it to be an alias to ubyte*/const(ubyte)* so that user couldn't pass > unicode string to an API that doesn't expect one. The same is applicable > to other APIs, too, for example, how does C stdlib co-operate with > Unicode? I.e. is core.stdc.stdio.fopen() unicode-aware?
Maybe we need a typedef! ;-)
