It seems that Fasm has a limitation of 256 chars for symbol names.
This is a big limitation though.
It's common that Microsoft compiler generates names which are longer then this and if you plan to work against existing compiled code there are lots of tricks you have to do to overcome this.

Here is an example a symbol of length 533 chars:

?_Isnil@?$_Tree@V?$_Tset_traits@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@U?$less@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@2@V?$allocator@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@2@$0A@@std@@@std@@KAAADPAU_Node@?$_Tree_nod@V?$_Tset_traits@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@U?$less@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@2@V?$allocator@V?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@2@$0A@@std@@@2@@Z

Is it possible that it can be extended to atleast 1024 for next version?

why don't you import it under shorter name?

Or what are you going to do with such long symbols?

This is about the only one limitation in fasm that is so deeply buried in internals that would require massive rewrite to extend it.

However I don't think this is really a problem - when you need to access the external symbols of longer names, or make some symbols public and give them longer names, you can use the extended EXTRN/PUBLIC syntaxes, like:

(scroll right to read the ending of the line )
and access that symbol inside the assembly source under SomeMoreFriendlyName.
More information on EXTRN/PUBLIC in section 2.4.3 of manual.

I'm trying to build a re-assembler tool. The idea is to process exising ms coff files to generate a asm file. This asm file must be compilable and link against existing object files produced by VC++ compiler.
I was targeting Masm at first which has the same symbol size limitation but due to lots of problems with masm I am retrying to retarget my output code for fasm instead.

In short I'm trying to build a tool which will generate the same type of code as VC++ compiler.

I'm both importing and exporting symbols. I am not sure if it will work with aliases since it's still something that has to interface the real world.

-- Henrik

Thanks for the quick reply. I'll give it a try and see how far I get.

-- Henrik

You use strings with byte-size (semi-pascal style)?

It's the limitation in preprocessor's source encoding scheme - it's already documented in guide to fasm's internals (it still lies here somewhere).

[EDIT]"Somewhere" means here: http://board.flatassembler.net/topic.php?t=3883 [/EDIT]