Re: Release of RosAsm V.2.025a

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.

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.

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.  That way I've got all of the debugging sup****t  
I've developed in every program without having to copy all of that code  
into every program.  However, like you've said, doing it that way is a  
huge disadvantage.  I'd be much better off to just copy and paste that 546
 
lines of code into every program that I write, that way if I later come up
 
with a better idea for some of the debugging stuff that's in there, I have
 
to go through every program I've made that uses it and update the  
debugging code seperately.  Being able to update them simply by updating a
 
single object file and a single include file would be a huge disadvantage.