You've been programming in a totally unnatural language ever since you wrote your first line of assembly language. Ask several assembly language programmers to jot down how to do something using DOS or BIOS and their answers will probably look similar. To illustrate this point, let's look at a couple of examples:
One of the first things you'll notice in these examples is the use of the equal
sign to indicate assignment or
MOV. Isn't it peculiar that
everybody knows exactly what is meant by the equal sign,
but the assembler forces you to use the mnemonic
When you take into account that
MOV is by far the most
common instruction used in an assembly language program that's a whole lot
of extra work. Extra stuff for you to think about, to write, to read. It's a real
waste of your time, not to mention disk space and bandwidth as well. Notice
that the examples above also are written with more than one "thought" on a
line. And why not? The meaning is clear and it conserves vertical space.
There is nothing inherently wrong with placing more than one thought
on a line, assembly just doesn't lend itself to that style.
These are just two cases where a natural intuitive syntax is used in everyday
communication between assembly language programmers, but when it comes
time to actually write the code, you have to conform to a primitive syntax
devised some forty years ago! Wouldn't it be nice to be able to use the
symbols you've been using your whole life, like
/, etc., to convey your
ideas to the assembler?
Well, pinch yourself, you're not dreaming, it's all true! The future is NOW! The programming language you've been dreaming of is:
If everybody was using and you asked the same questions mentioned above, the answers might just look like:
© . All Rights
The word OPTOMIZED, the name TERSE, and the logo are Trademarks of .