Why the resource file is embedded in FASMW.ASM? Wouldn't be easier to make changes if the resource file (that is, the menu and so on) were in a separate file?

Don't get me wrong. I'm just trying to understand, not to contest.

1. I, personally, do not believe that a seperate resource file would help; after all, it is about the same, anyway.
2. A seperate resource file would:
as an RC: require a seperate RC compiler, which would make FASMW non self-compilable
as a RES: be much harder to edit for those who do not have a RES editor (XN Resource Editor, ResHack etc.)

From my point of view, editing a separate RC file, even using a separate software, gives me a visual clue about where to put the controls. I've never edited resources manually, as text files. How one does that?

I got used to "divide-et-impera" method, which I personally think it's a good one. The fasm code uses separate inc files, isn't it? While it's about the same, there are still separate files. Well, why fasm code has separated inc files, but not resource files? Is the compatibility the only reason?


After all, I believe (please, correct me if I wrong), that even an external software will write the same text, except for the numbers that indicates the position of the controls.

If the rc file is a text file, fasm will still compile by itself, no matter what software it was used to create it. But, being separate, it can be modified manually or visually.

No offense, but you should have read my post: an RC would require a seperate RC compiler.

I read your post. I just forgot to add the last paragraph. My appologies.

Would require, for programmers who don't edit manually (because they don't know or they don' wont). Making a separate file will add another choice, beside manually.

Is it not the same problem with the .bmp and .ico from the resource folder?

Well, the '.bmp' and '.ico' are compiled resource files, which *can* be inserted using macros.