Re: Release of RosAsm V.2.025a

"Richard Cooper" <spamandviruses@[EMAIL PROTECTED]
> écrivait
news:op.sxcq9acx29jixb@[EMAIL PROTECTED]
 

> On Mon, 19 Sep 2005 05:56:48 -0400, Betov <betov@[EMAIL PROTECTED]
> wrote:
> 
>> No, he is not _wrong_. He is just introducing a _HUGE_
>> ADVANTAGE as an implicit inconvenient.
> 
> I don't see now not being able to do something can be an advantage.

Having a Tool that does not push the user to bad programming
practice _is_ in _HUGE_ advantage.


> When I write a really nice function, I like to be able to use it in
> every  program that I write, simply by making the file it's in part of
> the set of  source files that make up the program, or by using an
> include directive.   With RosAsm, I'd have to go and copy and paste it
> into RosAsm, because  apparently being able to keep it as a seperate
> file would be a huge  disadvantage.

Utterly wrong. With RosAsm, we store the "nice function" into
the Clip File, what is _WAY_ better and _WAY_ more intelligent
than going the "Blind-Box" programming way.


> I also don't link to external object code often.  Currently the only
> time  I do it is with my "quick little assembly programs" folder that
> I write  simple little programs in.  In there I've got my register
> dump code  compiled into an object file, and my script to assemble
> files links them  with that object file.

With the RosAsm methods, you don't _have to_ do it
this stupid way.


Betov.

< http://rosasm.org
>