Re: What "Unicode support" really means

Alexey Zakhlestin wrote:

I wonder why you mix "unicode strings used for the variables” and "unicode strings used for … array indices”. Second is not a problem, as array-index name is just a string which can have any characters which string has. In case of unicode support that means any unicode string. Only variable names are problematic.

Why? I don't like the way some OOP stuff works, but turning array indices into parts of function strings is something that people have been promoting. Download a query result from a database with unicode metadata and one ends up with unicode strings in both data and more important indices, which are then used as variable names and subsequently in function calls to that variable. Pierre's solution is to insist that the queries are re-written using 'AS xxx' where xxx is an ASCII string to get around the problem, but to my mind that is simply making the problem worse? People have to start thinking 'what can I actually use here' in other parts of the development process. I totally accept Marco's point about being able to work with other peoples code and not having the right keyboard, but I hit that problem even with ASCII - a simple '£' being a major problem at times. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk