music

OSdata.com

MILO as UNCOL solution

summary

    This is an attempt to get down in writing my recommended solution for the UNCOL problem before I die.

MILO as UNCOL solution

    This is an attempt to get down in writing my recommended solution for the UNCOL problem before I die.

    For information on the idea of a Universal Computer Oriented Language, see the article on UNCOL.

    MILO stands for Multiple Interwoven Language Operations. The name is not case senstitive.

purposes

    The core language presented here is made useful by accompanying tools. I don’t personally have the access to modern computers to build the tools, but I can define the core language.

    The original purpose for UNCOL was to have one central language so that there was only a need for one back end assembler per hardware computer and only one front end compiler per high level language. Each of these need to be built.

    Proprietary software would require the use both the front end compiler and one of each back end assembler for each target computer. This would allow the business to sell object code, which is much more difficult to reverse engineer.

    Another important tool is an install engine for particular computers. This would allow release of such things as drivers in a platform-independent manner, even for computers that don’t exist yet. There are a number of other items beyond device drivers where the owner has an interest in as wide a use as possible and has no strong desire to keep their software a secret.

    Another tool is a reverse compiler, which would take software in the MILO and convert it to a high level language rather than to an assembly or object language.

    One use of the reverse compiler is for legacy code. It would be possible to automate the conversion of old legacy source code into a modern programming language.

    Another use of the reverse compiler is for mutli-language programming teams. There is a huge productivity advantage if every person on a programming team can program in the language that he or she is personally most proficient at, but still allow sharing software between members of the team.

language problems

    There are a handful of language problems that tend to make the goal of UNCOL difficult. The following list includes some of the major problems. Note thatese problems are not mutually exclusive. They have a lot of overlap.

• over-specification
• under-specification
• side effects
• control effects
• unstated implications
• language imposed programming methods
• locking out new hardware features (such as parallelism)

contact

    If you find this interesting and want to contact me, write to Milo, PO Box 5237, Balboa Island, California, 92662, USA.

if you want to make a tax-deductible donation to the StarTree107 Foundation to support this educational work, contact Dr. Barry at 949-675-5778

    Challenge: Homeless or Facebook