FPC 3.2.2 - non Alpha Names of Classes and Members - possible ?

[paule32]

Hello,
Is it possible to give the Class's and Member's of a Class different Names with non-alpha Values (Char's) ?
How can I do this in the source code ?

[PascalDragon]

No, it's not possible.

[Khrys]

Like @PascalDragon said, it's not possible. Only strings matching  &?[^\W\d]\w*  can be identifiers.

You can prefix any identifier with a single  &  (for example to allow using keywords that are otherwise reserved, e.g.  var &Type: Char), so technically speaking there can be non-alphanumeric characters in the source describing an identifier, although this prefix is ignored in later compilation stages  —  e.g.  var A, &A: Integer  will generate a "duplicate identifier" error.

[paule32]

for some month's ago, I used objdump.exe to rename Symbols.
I don't remember me on the Details.
But with this Tool, I could do rename DLL Symbols.
If it possible with .o files - I don't know.
Yet.

[Khrys]

for some month's ago, I used objdump.exe to rename Symbols.

Classes and class members aren't symbols, so that won't help.

Perhaps what you're really after is renaming symbols of class methods, e.g.  CLASSES$_$TSTREAM_$__$$_COPYFROM$TSTREAM$INT64$$INT64  ?

[paule32]

when I do so with the Assembly Code, then I stuck in trouble with linking into a executable.
The Problem is not createing the Assembly Code, and compile to .o bject File(s).
The Problem is, that I don't know, how FPC link the .o bjects to an Executable.

FPC provide some Linker Scripts and Batch Files by given Command Line Options.
But when I execute the Batch Files, that contains Code/Commands to link the produces binaries to an Executable, some Magic opens and bring my mind flattered.

Maybe I should compile the .asm Files in a pre-task, before I include the .o in the Sources and then call FPC to link the Files to an Executable.
This could work.
But I don't let it a try, yet.

But I can looking forward, that could be not easy.

[PascalDragon]

You can prefix any identifier with a single  &  (for example to allow using keywords that are otherwise reserved, e.g.  var &Type: Char), so technically speaking there can be non-alphanumeric characters in the source describing an identifier, although this prefix is ignored in later compilation stages  —  e.g.  var A, &A: Integer  will generate a "duplicate identifier" error.

This is only an escape token, not a part of the identifier.

[MarkMLl]

for some month's ago, I used objdump.exe to rename Symbols.
I don't remember me on the Details.
But with this Tool, I could do rename DLL Symbols.
If it possible with .o files - I don't know.
Yet.

Bottom line: class and member names have to be valid Pascal identifiers.

If you have some very specific reason why they should not be, or where the external name should be presented with capitalisation other than the current convention, or where an exported identifier should have a different compiler-generated separator, then discussion might possibly be in the scope of this forum.

If you have a specific hack using external tools which allows you to use FPC-generated .so or .dll files in the context of some other language (or vice versa), or to tidy things up for a non-standard debugger, then getting it into the record is probably in the scope of this forum.

But I suggest that FPC's limited compatibility with C++ etc. and the private nature of member names etc. means that you must expect an uphill struggle if you're proposing any changes.

MarkMLl