Unified Programming Language 

The Unified Programming Language  would use a popular language as a
reference base. Any number of alternative languages and syntaxes could be
derived from it in such a way that they would be rather directly translatable to
and from the reference language, which would likely be C or C++.
 The derivatives could have various levels of difficulty: from assembler and C++,
to natural language, flow-charts (such as ProGraph and A-Flow), templates and
programming wizards.

 A byte-code language would be designed that the reference language could
be translated to directly, much as the JAVA language is designed. JAVA and
its byte code might even be the best candidate for the standard.

 Source-code or byte-code translators would be required for each derivative
language and syntax. but that should be a fairly simple matter to deal with.
 The granularity of the byte-code should accommodate everything from assembler
opcodes to perhaps complete programs.
 The system should accommodate custom libraries, so programmers needn't be
tied to the standard ones.

Having multiple-levels of byte codes would provide cross-platform capabilities.
The levels could include a high-level such as in JAVA, another such as Parrot
or MSIL .and yet another that corresponds more directly to various assembly lang-
uages.
 




Website Home
Project Summary Page at SourceForge.net






This project is sponsored by TheirCorp
(formerly TheirWare Corporation)