On 6-2-2012 21:30, Thaddy wrote:
Meaning/implies: when you are the compiler guardian/owner you can simply enforce string to unicode or ansi or ebdic or whatever based on the platform/os defaults. Like most of FPC already does. And leave it to the programmer to deviate by using the A alternative api. We could not do that since we do not have an underlying compiler to our kol framework. So we chose KolString. FPC can define it opaque as a compiler switch with a default.UNICODE} blocks. I propose FPC follows a similar strategy.We already did it for Kol, which has a (almost) totally opaque KOLstring/char type depending on switching on
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
