this thread is a fasm newbie thread

if I only could get these religious conservative trolls out of the thread it would become constructive.

Listen, there are people who want to move forward, and we don't want to move backward,

we don't want to participate in your temples where you worship old and ancient objects.

We want to move forward, including the author of FASM. Forward we go. That means, we're leaving you behind.

We're basically dumping you into the ocean, so that FASM can continue to evolve. Are you getting it. You are outdated, along with your very oldfashional friends and lunatics. We want to evolve, not stay behind. Please respect that. Now I don't have anything particular against you conservative people, other than that you're unable to adapt anymore.

It smells of elderberries and Tomasz want a fresh future.

But listen carefully to what I have to say about this, take it seriously. "If you let the macro system take over everything with the assembler, people will stop appreciating macros and they will lose respect of it".

People will get respect for the macro system, when they can use it in small things.

A powerful macro assembler, and a loveable macro assembler is one the user can use without the actual need to use macros, in that way, macros become a luxury.

I read through the list builder, I understand the concept. You basically take over the charge of defining the sections from inside your own macros, and thereby you can also control the order of defined data. It's smart and I like it.

But apart from that, if we go back to a fasm-point of view, the goal of a macro engine of an assembler (in my opinion), is to make it powerful and flexible, but once you need a macro to strongly override the default behavior of an assembler, time has come for standardization.

You could use "LABEL ... AT ..." construct for this purpose, in fact the only difference between numeric symbols defined with LABEL and = is that the former cannot be redefined.

flat assembler version 1.71.39 (3145344 kilobytes memory)
label x at 1.0
error: invalid value.

For integers this works well. For floats it struggles.

I'm not going into a religious debate with you, this thread is a fasm newbie thread with questions about fasm, if I only could get these religious conservative trolls out of the thread it would become constructive. Listen, there are people who want to move forward, and we don't want to move backward, we don't want to participate in your temples where you worship old and ancient objects. We want to move forward, including the author of FASM. Forward we go. That means, we're leaving you behind. We're basically dumping you into the ocean, so that FASM can continue to evolve. Are you getting it. You are outdated, along with your very oldfashional friends and lunatics.

The author of FASM is too young to be stuck with an old idea, he too wants to move forward, but you are keeping him stuck. He is too young to be stuck, his mind is too brilliant to be stuck, he wants to use his mind, not let it rot at one particular position in his life. We want to evolve, not stay behind. Please respect that. Now I don't have anything particular against you conservative people, other than that you're unable to adapt anymore.

It smells of elderberries and Tomasz want a fresh future.

It seems like you know FASM already because you're requesting changes...

and yet you are a new bie. And I'm neither conservative nor liberal. I'm just an endangered heterosexual male now that the whole country is turning to rear deliveries and rainbows. Oh, and how was the pride March?

The reason those macros exist is because fasm can generate an EXE file directly. If one is using a linker then it is the linker's job to rearrange and merge things.

If you need it, fasm still supports the "standard" sequence of assembling and then linking. In that situation you don't need those macros to merge sections together.