Re: The Case Against RosAsm (#2)

From: The Half A Wannabee ("The)
Date: 01/21/04 

Date: Wed, 21 Jan 2004 11:44:40 +0100

"Beth" <BethStone21@hotmail.NOSPICEDHAM.com> wrote in message
news:X1sPb.820$NU2.288@newsfep3-gui.server.ntli.net...
> Gerhard W. Gruber wrote:
> > Beth wrote:
> > >The machine instructions are explained in their own section and the
> > >"HLLisms" like "IF" are in a different section again...and all of
> this
> >
> > I don't see why a assmebler needs an IF. Of course some things like
> > structures, or easier function calls like in a HLL is quite
> convinient, but
> > IF, WHILE, FOR and such constructs are taking away the control of
> the
> > programmer IMO. Of course I guess even in HLA you may not be forced
> to use
> > this if you don't like.
>
> Indeed; And I don't ever use any such constructions...neither would
> any beginner who properly follows AoA, which only uses these things at
> the start as "crutches" but gets around to showing how these
> statements work and their machine instruction equivalents...
>
> You're quite right; HLA "enforces" no such thing at all...
>
> Whereas, Rene does _force_ people to "obey" his philosophy of "no
> library code" and so forth...

How can he ? You got the source code. In a year, when I get more knowledge,
I can add in whatever I want. Whats wrong with loadlibrary and
getprocaddress ? Nothing. Speed ?
It allready has demo code for how to access com right ? So I can do whatever
I want cant I ?
But do I want it ? If can be avoided, no.

I cant understand how anyone can critic a product so easy to learn as Spasm.
There is not one thing in there that is like "stupid". Its so good, that you
dont even notice how good it is. I mean the search, expand features, Title,
multi intruction lines. Use of D$ instead of DWORD PTR[] is only a good
thing. Monofile, is only stupid when you have stupid feature to get around
in it. The treee stucture, the right click, etc, gets you anywhere i 0 time.
(And titles tab section) And it was much easier to learn to addess memory
with Spasm, then with basm/intel syntax.
The debugger that most times let you step inside even the api, lets you peek
the memory of every variable and register. It has maximum functionality for
minimum helpfiles to read. Its intuitive. It follows the way I think.
Setting a break point means adding int 3 at where you need a breakpoint. You
cant fail there.

Last night I read the optimize sections of the help. Brilliant philosofy. I
steal it.

I dont comment on the rest.