Re: Release of RosAsm V.2.025a

Betov wrote:

> On a News Group devoted to Assembly and Assemblers,
> i am founded to presume that the readers are supposed
> to have heard of the differences between Mono-Pass and
> Multi-Pass(ses) Assemblers, which is the acception in
> which i made use of this formulation. That is, what
> is Mono-Pass, is the Assembler Encoder. For the computation
> in charge of the JSO, it is, evidently executed as many
> times as needed until no more "Long to Short" possible
> case could be found.

Thanks, that's a little clearer. It's definitely a language thing then. So

to sum up, Rosasm has the ability to assemble in a single pass, but takes
as 
many p***** as necessary to do the job.

> Would this additional Computation be made default, in
> RosAsm Assembler, the whole Assembler would remain
> Mono-Pass, and the Compilation speed would remain the
> same, with this emulation.

Can you explain to me what you mean by the term "emulation"? I have my own

ideas of what it means, but as has been the case before now, my 
understanding is likely to be different to yours. By "emulation", I take
it 
to mean a process that behaves like a system, produces the same results as

that system, but comes to those results by a different method than that 
system would employ. If a process uses the same methods as that system
then 
I take it to be a "simulation" rather than an "emulation".

(This is mostly because of my background in writing emulations of the Z80 
processor, which behave like a real Z80 would, but obviously don't perform

the functions at the level of gates and signal routes through the 
processor - they take the opcodes and produce the results of that opcode 
through calculations).

Thanks.