Summary
What if you could write Python code with an alternate interpreter/preprocessor that allowed you to use different keywords in your native tongue, including ideogrammic languages? This proposition comes from a thought that Python semantics may be flexible enough to act as a VM for the new CEDSimply language.

I introduced the concept of flexible syntax in English-centric Programming Languages vs DSLs and mentioned the origins of CEDSimply earlier.

This morning I woke up with a very compelling thought - feel free to tell me I'm still just dreaming :-)

It comes together something like this:

1. the semantics of Python's textual representation are compatible with CEDSimply (semantics yet to be published)
2. the CEDSimply ability to use different "dialects" or "vocabularies" would therefore allow you to write Python in a native tongue but still translate it to English Python for a different consumer
3. having a CEDSimply implementation on top of Python and thus directly able to be deployed in any Python implementation includes some very big batteries!

So, is the thought of a multingual Python appealing?

Talk Back!

Have an opinion? Readers have already posted 2 comments about this weblog entry. Why not add yours?

RSS Feed

If you'd like to be notified whenever Andy Dent adds a new entry to his weblog, subscribe to his RSS feed.

Digg | del.icio.us | Reddit

About the Blogger

Andy is a free-lance developer in C++, REALbasic, Python, AJAX and other XML technologies. He works out of Perth, Western Australia for a local and international clients on cross-platform projects with a focus on usability for naive and infrequent users. Included in his range of interests are generative solutions, software usability and small-team software processes. He still bleeds six colors, even though Apple stopped, and uses migration projects from legacy Mac OS to justify the hardware collection.