{$DEFINE} has lower priority than {$INCLUDE %FILE%}

[zex2011]

There are compiler directives {$INCLUDE %FILE%} and {$INCLUDE %LINE%}

They DON'T load files. Instead they insert [current file name] / [current line] at compile time. So you can make something like this:
DebugLn ('Error in file ' + {$INCLUDE %FILE%} + ' on line ' + {$INCLUDE %LINE%});

I wanted to make this shorter, to avoid repeating the same long string everywhere in the code. So I wrote a macro like this:
{$MACROS ON}
{$DEFINE ErrorInfo:='Error in file ' + {$INCLUDE %FILE%} + ' on line ' + {$INCLUDE %LINE%}}

DebugLn (ErrorInfo);  // this should write the current file and line number

But this doesn't work. The problem is that $INCLUDE executes first so it inserts a fixed file name / line number during the macro declaration. Wherever this macro is used, always the same (incorrect) data is displayed. Not the current line, but line where macro was first declared.

If anyone has experience with FPC macros I'd like to know if there's a way around this?

[Blaazen]

Probably it is not possible. I found little related question on fpc mailing list:
http://free-pascal-general.1045716.n5.nabble.com/advanced-macros-td2823767.html

[Murmandamus]

It is a pre-processor feature, which means it is only evaluated once at compile time. You'd need a way to escape the {$INCLUDE x} variables so that they are re-processed when the macro is expanded.

[marcov]

Free Pascal is not a preprocessor heavy language and not considering changing that.

If you have a need for very complex preprocessing, it is best to use an external preprocessor.