Do you want:
1) the compiler to accept source code in UTF-8 character encoding? 2) compiled programs to read and write characters using UTF-8 character encoding?
#1 can be done with “gsc -:f8 …” #2 can be done by starting your program with the shebang “#! /usr/bin/env gsi -:t8,f8,-8”.
A configure option could be added to set the default character encoding.
Should the system obey the LC_CTYPE or LC_ALL variable? Good question! Is this “expected” behavior? It wouldn’t be hard to implement, and still allow overriding with the runtime options. However, gsc and gsi will become more fragile and dependent on the run time environment…
What’s best?
Marc
On Jul 27, 2017, at 3:40 PM, Faré fahree@gmail.com wrote:
Is it possible to build Gambit such that UTF-8 is the default for I/O? Or should it heed the LC_CTYPE or LC_ALL variable?
I had a bug while compiling gerbil code that vyzo traced to disagreement between I/O options used by gambit and gerbil. The workaround was to export GAMBOPT=t8,f8,-8 rather than fight to propagate the proper options to gsc. I would like to build gambit with these options as the default, so I can distribute a version that works out of the box.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org He wa'n't no common dog, he wa'n't no mongrel; he was a composite. A composite dog is a dog that is made up of all the valuable qualities that's in the dog breed — kind of a syndicate; and a mongrel is made up of all riffraff that's left over. — Mark Twain _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list