The "@longcode" tag makes incorrect code display.

[opensimply]

There are two issues with @longcode tag.

1. Bold for the identifier after the qualifier in the dot notation, if the identifier is called "Name".
2. Various coloring of numbers when explicitly specifying this color in an external style file., like span.pascal_numeric {color: blue;}

longcode.zip

[michaliskambi]

AD 1 - Indeed. The Name is detected as a standard directive, as in procedure Foo; external name 'Foo2'; .

I didn't fix it yet (we could hardcode a condition that "identifier after dot is never a standard directive", but it would need to be checked whether it doesn't make any regressions).

AD 2 - Floating-point values have style pascal_float. So use something like

span.pascal_numeric, span.pascal_float { color: blue; }

to more reliably color all numbers.

Moreover, our @longCode scanning code didn't recognize numbers in the scientific notation. I fixed that now (fixed in 8075a29 , acb26a4 , testcase added in 5c9a9b3 ).

So this is half-fixed now.

[opensimply]

Thank you. Should I close this ticket?

[michaliskambi]

Let's leave it open for now. I'd like to fix Name highlighting (I suspect other Pascal standard directives are similarly affected) at some point, it just needs time to test. I would introduce similar logic for @longcode and our PasDoc_Tokenizer ("identifier after the dot should not be treated as a standard directive") and see does it cause any regressions on pasdoc testcases and Castle Game Engine. If not, it would be probably OK solution.

[opensimply]

Good luck with your coding!