I agree that documenting a program like FASM isn't an easy job, but at least you can make the task easier by including comments that describe macro or procedure behavior. That will enable us to spend time writing code rather than deciphering how a macro works or what parameters should be passed.

For example:



How much sense does that make? For a beginner to Windows programming, not much actually. Please use some comments to describe every macro that has been written instead of just providing the code.

evil. =)

Would detailed documentation of macro purpose and usage (as a block comment before each macro) be enough, or you want also comments for the inner mechanism of macro?

Documentation for purpose and usage would suffice for me. =) Thanks Privalov.

On second thought, documenting "tricks" you use in the code might prove beneficial too. =)

I think the macros section of the fasm documentation is incomplete. It's annoying not being able to access the untapped power of the macro system because some features aren't documented.

Features are documented. It's the tricky use of the features that is not documented.