On Sat, 31 Mar 2012 06:54:30 +1100, "DonH" <
donlhu...@bigpond.com>
wrote:
There are such character sets/mappings, for example, Latin-1. But that
would hardly resolve the issue.
A few exotic attempts have been made to create 'bilingual' or
'localized' programming languages , however, those were mostly just
scripting front-ends for a 'single language' compiler (ie, a
pre-pre-processor) and pretty much a failure. This excludes those
attempts where a parser/compiler is converted to another language. For
example, there are Russian and Chinese versions of BASIC - but they
would be as mystified with English as your QBasic is with Greek.
In general no such a thing exists in programming. The main problem is
Keywords and Libraries. Imagine the complexity that would be
introduced if ...
SI(...)
SE(...)
AV(...)
IF(...)
may or may not be indicating an "If" block.
What if a Spanish programmer passed his source code across the border
to his Portuguese buddy for additional coding, who then passed it on
to England? You would then have code full of SI(...), IF(...), and
SE(...) blocks all meaning the same thing. Not only would the number
of Keywords and Library name space expand but the code itself would
turn into a jumbled mess.
Not to mention the fact that choices for creating a non-keyword
variable would decrease considerably. <g>
-ralph