Micha Nelissen wrote

Hi, Why is the define NEW1_1 used to indicate the fpc 1.1 compiler? The compiler defines VER1_1, not NEW1_1.

JUst a month ago or so there was a discussion on this list on the hows and whys of NEW1_1. I didn't follow the discussion in every detail, but as far as I can recalll, NEW1_1 was a way to manually enable things for the 1.1 compiler. The reason for manually doing so was that those pieces of code weren't compatible with certain versions of the 1.1 compiler. Checking against a VER1_1 directive wouln't have helped here.

Marc

Hi,

Why is the define NEW1_1 used to indicate the fpc 1.1 compiler? The compiler defines VER1_1, not NEW1_1.

Regards,

Micha.

Lazarus (at least synedit) can not be compiled with current snapshot fpc 1.1 compiler. It can be compiled with the (quite outdated) fpc 1.1 compiler found on the web site. Both compilers define VER1_1. But the web site fpc 1.1 uses more fpc 1.0-like constructs. So there is code for fpc 1.0 and fpc 1.1website, which must go in one {$IFDEF} branch, and code for the new fpc 1.1 compiler which must go in another branch.

If there is a fpc 1.1 compiler that can compile lazarus, the website compiler can be updated and we could use VER1_1 to make a difference. For more info see also the utrace.pp file in the lcl-directory.

HTH,
Vincent.