Carel Fellinger wrote:
Quite to my surprise I got a linker error with a module named "files":
/usr/lib/gcc-lib/i386-linux/2.95.4/libgpc.a(files.o): In function `init_Files': files.o(.text+0xb28): multiple definition of `init_Files' general/target/files.o(.text+0xea4): first defined here /usr/bin/ld: Warning: size of symbol `init_Files' changed from 99 to 67 in /usr/lib/gcc-lib/i386-linux/2.95.4/libgpc.a(files.o) collect2: ld returned 1 exit status
Changing the module name to e.g. "ffiles" get's me around this, bummers that I've to change the name in all imports.
What other (module) names are forbidden in my code?
And is there any change that a future release will do better then to polute my namespace with module names I didn't (explicitly) import?
The names were not forbidden intentionally. I hadn't noticed this asmname conflict of the initializers. It will be fixed in the next release. Thanks for the report. (carel1.pas)
Frank