On Wed, Nov 03, 2004 at 01:01:51PM +0100, Jonas Walldén @ Pike developers forum wrote:
If you know your input is UTF8, simply call utf8_to_string() before handing the data to the Pike glue.
It means - more CPU usage, more load, more memory for buffers, and all this only to pass on data through Pike? Does it makes _any_ difference to Pike - the meaning (contents) of any _binary_ string? Why I should make all those conversions when I can simply pass data as is?
BTW, most (if not all) current database interfaces (in Pike) will (most probably) fail if I'll use strings wider that 8-bit.
May be this is my specific case, but I've an applications with really high load (gigabytes of data), so obviously I don't want any unnecessary conversions, if I can avoid this (most, but not all of the data is not processed nor checked, just pupmped through).
And, back to original problem, in spite of recent comments - if Pike _forces_ user to use Unicode strings (16- or 32-bit wide), why this is not enforced _everywhere_ but only in SQLite? :)
Regards, /Al