Re: Report from the LuxAsm mailing list for Betov

Randall Hyde wrote:

If LuxAsm is using *separate* programs for these functions, there should be
no problem. That is, the assembler module could crash during assembly and it
wouldn't affect the editor (and the file it currently holds). The problem
with RosAsm is that it is all one monolithic program. If one line of code
crashes, the whole system comes down and any unsaved work is lost. This is
true whether the crash occurs in the editor, the assembler, the
disassembler, or in the ASCII chart display.

A way around it would be to save or backup the current contents of the editor before performing any action. I don't know if RosAsm does this, but it would be doable even in a monolitic system.


But as long as LuxAsm is simply
a "driver" program, that invokes all these other processes independently, it
is sufficiently decoupled that the problem does not exist.


If one of the external modules crashes, it can still stall/timeout the
editor.  It's still a good idea to save the sources before performing
any action.  A way around it would be to start a timer before creating
a new process and destroy the process if it times out.

As for Rene's comments about "it's just another 'brick & brock' IDE"
(whatever that means, it must mean something in French because it doesn't in
English), well, he's always complaining about things he doesn't understand.
And the fact that he wouldn't have a clue to to properly design an IDE
system is the same reason he bitches about products like LuxAsm or RadAsm.
Cheers,
Randy Hyde


Hey, if it ends up in Rene's ***-list, you know you're doing something right!

--
[kain]
http://www.geocities.com/kahlinor
.

Quantcast