Re: ///Wannabee Rants

På Tue, 09 Jan 2007 01:35:03 +0100, skrev sevag.krikorian@xxxxxxxxx <sevag.krikorian@xxxxxxxxx>:


For me, it's about 90/10 HLA/FASM. FASM still lacks type-checking
facilities.

Why are theese so important?

As for RosAsm, as soon as the macros system is improved
with type checking for user defined types and it can generate object
code, I'll give it a serious spin.

How could type-checking make any sense in asm?

mov edi D$esi + Objects.Current

In this case I know that "Object.Current" is an equate, pointing at a Paragraph object, or an object part of the "tree" that Paragraph object belongs too.

It close to impossible for me to try to parse a list containing objects not allready compatible, unless I make an error. So therefore, in the event I could make a bug that cases ESI to point at some villain memory, how could type-checking be of any use?

Suppose ESI was written by a bug, like this : "pop esi", how could RosAsm detect that the correct type has present in the stack, at compiletime?

?

I do not understand this type-cheching thing, or why and how it could be any advantage in asm.

In addition, if i make a procedure :

Proc SaveObject:
Argument @BaseObject
mov edi D@BaseObject
BaseObject.vCall vSaveObject
EndP

And if I then called it like this:

push edi | call SaveObject

and edi was (because of a bug) containing a perverted pointer, maybe the bug was done a lot earlier.

How could RosAsm detect this ?





-sevag.k
www.geocities.com/kahlinor




--
Poetry, Art, Philosophy....does not represent any kind of shielding from evil. Hitler loved Wagner.
.