[SOLVED] Howto use a DEFINE present in an installed package

[MarkMLl]

The syntax highlighter and the compiler can differ in opinion. Make sure you test it by running a compiled binary and printing or logging the result.

I was tempted to point that out: different programs, different projects, different developers...

However more important is consideration of the compiler mode.

MarkMLl

[tintinux]

The syntax highlighter and the compiler can differ in opinion. Make sure you test it by running a compiled binary and printing or logging the result.

Ah, when compiling, it is OK...
The syntax highlighter was wrong.
Thanks to all.

[PascalDragon]

Depends on the mode.

The content of an expression is restricted to what can be evaluated at compile-time:

*    Constants (strings, numbers)
*    Macros
*    Compile time variables (mode MacPas only)
*    Pascal constant expressions (mode Delphi only) <=====

That should be updated, cause the only mode where Pascal constant expressions are not supported/enabled is mode MacPas. All other modes allow them.

https://www.freepascal.org/docs.html -> Programmer's Guide detailed discussion of $IF. It's safest that I don't put in a URL for that since there's no guarantee that if will remain consistent over different versions of the compiler.

You could have at least mentioned the title of the section however, this way one doesn't need to guess where exactly you found it...

[MarkMLl]

You could have at least mentioned the title of the section however, this way one doesn't need to guess where exactly you found it...

Wearing my technical writer's hat: I agree in principle, but the problem is that section header text (not to mention URLs derived from it) can be very easily broken.

On the "teach a man to fish" principle, in this context I think it's more useful to highlight the documentation root- which a lot of people overlook in favour of the wiki- plus some brief hints on how to use it.

MarkMLl

[PascalDragon]

You could have at least mentioned the title of the section however, this way one doesn't need to guess where exactly you found it...

Wearing my technical writer's hat: I agree in principle, but the problem is that section header text (not to mention URLs derived from it) can be very easily broken.

It would have nevertheless allowed to look it up right now instead of having to search it which costs time that can be spend better.

[bytebites]

But principles are good if they make life harder.

https://www.freepascal.org/docs-html/current/prog/progsu126.html#x139-1400002.4.1