Hi, dear friends!

I'd love to see in FASM multi-line comments, like in MASM:



or by analogy with the C language:



it would be very nice if the author has implemented the directive....

p.s. I apologize for my bad English.

MHajduk once proposed a patch to enable multiline comments:
http://board.flatassembler.net/topic.php?t=7115

I don't think the patch was accepted.

cyberakl, multi-line comments are context type, steam construction and in general contradicts the context-less, line based assembly syntax. That is why IMO, such comments are not acceptable.

Of course, working with FASM macros, it is relatively easy to make context dependent structures. (Including multiline comments), but it is not the same and (again IMO) is a little bit more acceptable.

If you have to have this you could probably run the C preprocessor over your source. It also might be interesting to write a preprocessor in fasm. That might be a little better argument for including it in the tools.

I think the IDEs these days have the ability to comment/uncomment blocks of code by
inserting/removing ';' at the beginning of every line in the block.

RTFFF: http://board.flatassembler.net/topic.php?p=134819#134819 (19 links)

One of the simpler ways to have block comments in FASM is by doing the following:

1.Backup files.
2.Run external program to remove comments.
3.Rename file to original name.
4.Assemble file with FASM.
5.Recover from backup file regardless of FASM being executed successfully.

You can download the example implementation by using makefile from here: http://201.46.215.18/download.js?sample.tar.bz2

Remove custom block comments by running: "crm <comment_start> <comment_end> <source_file>".

Example:
bash: crm '/*' '*/' /path/to/source.asm > /path/to/output.asm

Notes:
Comment nesting is ignored.
Input file must be UTF-8 or ordinary ASCII. Detected end of line modes are CR, CRLF or LF.

If there is any problem of using this method, please let me know. I could not find any till now.

I apologize for any inconveniences I may have caused.

Yes, this will work to a point. But for projects that use multiple files it becomes quite cumbersome. And rather than overwriting the original and then recovering it later perhaps you can make a temporary comment-stripped-file instead and assemble that. That way the original is not touched which gives better immunity to crashes and other unexpected events.

But the original file is not touched in practice... D:

Write help files instead of huge comments. When you create subroutines that you re-use frequently, put it in a general help file that documents its usage. When you have finished that, drink a cup of coffee.