High Level Constructions ?

[nobody]

Hello to all developers

It's good to see nasm in progress again. Many masm users find it diffucult to write code without contructions like IF/ELSE/ENDIF. I wish nasm has build-support to those contructions. I don't like doing that in macro way. Is there a way to include  Bryant "Synfire" Keller 's nasm32 macros internally into nasm preprocessor. Wouldn't it be a good adaptation. Maybe in that way many masm programmer move to nasm.


regards
:-)

[nobody]

> Hello to all developers

Strictly speaking, the development team ought to be addressed on the "nasm-devel" list here at SF. But some of 'em read this forum...

> It's good to see nasm in progress again.

Agreed!

> Many masm users find it diffucult to
> write code without contructions like IF/ELSE/ENDIF.

Yeah, seems so.

> I wish nasm has build-support
> to those contructions.

Why? The CPU has no equivalent. You want "high level", use C!

> I don't like doing that in macro way.

Why not?

> Is there a way
> to include  Bryant "Synfire" Keller 's nasm32 macros internally into nasm
> preprocessor.

Probably. See "standard.mac".

> Wouldn't it be a good adaptation.

I don't see why.

> Maybe in that way many masm
> programmer move to nasm.

AFAIK, the MicroSerfs *like* their enslavement. If they aren't willing to learn assembly language, or at least "%include macros.inc", that's *their* problem, not Nasm's!

Alternative viewpoints welcome!

Best,
Frank

[nobody]

On one hand, including hidden Macros would massively _degrade_ NASM, as an Assembler, and, on the other hand, doing so, in the hope of having MASM users switching to NASM is completely absurd: The programmers who choose MASM have reasons for doing so, and these reasons have zero relationship with MASM hidden Macros, or anything like this. No Assembler on earth will ever please these guys, would it be 100% compatible with MASM, would it remove its limitations, and would it be twice better.

In short words, these guys choose MASM, because it _is MicroSoft_, and because it is anti-ethical and anti-GPL. Believe it or not.


Betov.

[nasm64developer]

> Is there a way to include Bryant "Synfire" Keller 's
> nasm32 macros internally into nasm preprocessor.

A user is always free to %INCLUDE those if/when needed.

That said, they should not become part of standard.mac
because that would force them upon everyone -- which is
not the right thing to do.

In fact, standard.mac is "too fat" already -- it should
only contain constants, variables, and functions; macros
that add support for alignment, structures/unions/records,
or control flow, should reside in a separate and optional
include file (which would be part of the NASM package, but
not built into the assembler itself).