Forum > General
[SOLVED] Howto use a DEFINE present in an installed package
MarkMLl:
--- Quote from: marcov on December 02, 2024, 03:38:19 pm ---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.
--- End quote ---
I was tempted to point that out: different programs, different projects, different developers...
However more important is consideration of the compiler mode.
MarkMLl
tintinux:
--- Quote from: marcov on December 02, 2024, 03:38:19 pm ---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.
--- End quote ---
Ah, when compiling, it is OK...
The syntax highlighter was wrong.
Thanks to all.
PascalDragon:
--- Quote from: MarkMLl on December 02, 2024, 09:42:15 am ---Depends on the mode.
--- Quote ---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) <=====
--- End quote ---
--- End quote ---
That should be updated, cause the only mode where Pascal constant expressions are not supported/enabled is mode MacPas. All other modes allow them.
--- Quote from: MarkMLl on December 02, 2024, 09:42:15 am ---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.
--- End quote ---
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:
--- Quote from: PascalDragon on December 03, 2024, 09:42:38 pm ---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...
--- End quote ---
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:
--- Quote from: MarkMLl on December 04, 2024, 09:43:08 pm ---
--- Quote from: PascalDragon on December 03, 2024, 09:42:38 pm ---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...
--- End quote ---
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.
--- End quote ---
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page