Hi,
I strongly encourage everyone using v11 to use Unicode mode. Non-
Unicode mode is essentially a hack -- internally 4D is always using
Unicode throughout (including the data in the database). When you run
in non-Unicode mode you are forcing 4D to constantly convert to and
from Mac Roman -- every time you read and write data, and every time
you read and write strings in the language. Essentially you are asking
4D to cripple itself -- and waste a lot of time doing so.
The real killer is when you pass text/string arrays from a non-Unicode
database to a Unicode plugin (such as Active4D). 4D has to copy the
entire array, convert each element, pass that to the plugin, and then
after calling the plugin do the same in reverse.
Please note that Active4D v11 is ALWAYS in Unicode mode. You may not
be able to access 4D process or interprocess text/string variables in
Active4D if the database is in non-Unicode mode. I haven't tested this
yet.
I sense something approaching fear or scorn in some of the responses.
Unicode is nothing to fear, in fact it should be embraced. EVERY
operating system and EVERY major development platform outside of 4D
uses Unicode, it's about time we in the 4D community catch up (kicking
and screaming). Unicode may be new, it may be unknown, but it is
nothing to fear.
Please note: I DO understand that many of you are under time
constraints and don't feel you have the time to deal with issues that
*may* come up with the switch to Unicode.
Regards,
Aparajita
www.aparajitaworld.com
"If you dare to fail, you are bound to succeed."
- Sri Chinmoy | www.srichinmoy.org
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
