"Enable preprocessor parsing" should be enabled by default in JCF, as perfectly valid code is often unformattable without it
Original Reporter info from Mantis: Akira1364
-
Reporter name:
Original Reporter info from Mantis: Akira1364
- Reporter name:
Description:
Particularly for someone who might be a newcomer to Lazarus, I don't think it would be even slightly obvious that "Enable preprocessor parsing" not being checked is the actual reason the formatter is failing on their code.
At the surface level it moreso just tends to appear that the formatter is simply not "good enough" to handle defines properly in that scenario, even though that is not the case.
I'm not sure why "Enable preprocessor parsing" even exists, frankly... I can't see what the advantage of ever having it disabled would be.
Steps to reproduce:
None specifically needed.
Mantis conversion info:
- Mantis ID: 38498
- OS: Windows
- OS Build: 10
- Build: Any / Trunk
- Platform: x86_64
- Version: 2.0.10
- Fixed in revision: r64636 (#6b75fab6)