Re: Definitions - What are yours?

On Jul 31, 11:30 am, Betov <be...@xxxxxxx> wrote:
"rh...@xxxxxxxxxx" <rh...@xxxxxxxxxx> écrivaitnews:1185906076.410987.264290@xxxxxxxxxxxxxxxxxxxxxxxxxxxx:

You understand it or not, the Assembly Types exist,
and you will never succeed to change them.

Who's changing them?

You.

Last time I checked, HLA supports all the "assembly types" you're
talking about.

:))

The problem is with the other types, that have no counter-parts
in Assembly, because no counter-parts in the dead file.

So tell me, what makes "byte" so special? What does it matter whether
I call it "byte", "bits8", "octet", or "int8"? It's all exactly the
same thing. In Computer Science, this is known as an "isomorphism" and
it doesn't change the semantics one bit.

Of course, if you're so hung up on calling things "bytes, words, and
dwords" be my guest. Just understand that all you're doing is
demonstrating your ignorance of computer language design and while a
few people who operate at the same level of ignorance as you do might
buy the argument, most people will simply think you're a crackpot.

You may as well argue that labels ought to consist of an "L" followed
by the machine address of where that label refers in memory. If you're
not going to allow meaningful names for types, why allow meaningful
names for labels? For that matter, why not rewrite all the mnemonics
using their hexadecimal opcodes? Again, if you're not going to allow
the programmer to attach meaningful names to their types, why not
apply this concept to everything?
hLater,
Randy Hyde


.