dummzeuch

I hereby apologize to Embarcadero. They replied on the same day to our general purchasing account (which was correct because that is the email address used to register the licenses). Somehow I must have missed that reply several times when I looked there. And I managed to fix the problem too, even though I am still not sure what I did wrong the first time. And thanks to Devid Espenschied for clearing that up.

Thanks for the reminder. I had totally forgotten about Devid and have now contacted him directly. (You might want to remove his email address from your post to prevent spam.)

So far most of the libraries only needed very little changes when a new Delphi version came out. Mostly it was adding a new compiler version to a central include file. In the case of the JCL that file would be jedi.inc. Hypothetically somebody else might have done that already when you join a beta program and posted a link to the updated version in the also hypothetical internal communication channel. (Hypothetically because 1. I am not in the current beta (Haven't received an invitation yet) 2. Even if I were, the NDA would prevent me from telling about it, but it stands to reason.)

I filed a support ticket with Embarcadero two days ago regarding a problem with license hosting on the ELC. I haven't heard from them yet. How long does it usually take them to get back on such issues? Previously I got an answer from Embarcadero Germany with a similar problem, but since Matthias Eissing is no longer with us, hopefully somebody else has taken over that job.

I still don't understand the problem of detecting whether dcc32 of a CE installation can compile anything. What does it do if you give it an empty .dpr file to compile from a cmd window? Does it just silently fail? No error message? But even if that is the case, you could at least try to compile said empty .dpr file and check whether an executable is created. Not quite an elegant solution but it should work.

Does the executable dcc32.exe exist in that case? If not, there's your answer. If yes and it only outputs an error message or something, you could do exactly that: Call it and check for that error.

And that was most likely the reason. The compiler only compiles units that have changed. Changing the include file does not change the units. To ensure that a unit is recompiled after a change to an include file, you must do a complete build of the project(s). The same applies to defines set in the .dproj file btw. Changing them does not trigger a complete rebuild. If you want to be really paranoid about this, delete all units from the unit output path. This ensures that every unit will be recompiled. I do that once in a while.

You cannot define a symbol in the .dpr file to be available in the units (it will be available in the .dpr file itself though). You must put it into the .dproj file (Project -> Options). Alternatively you can define it in an include file and include that file in all units that require the symbol. That latter approach is used by most libraries because a library cannot add anything to the project options.

All tests pass with 10.4 now.

Interesting: Completed: 205, Succeeded: 205, Failed: 0 ✓ All tests passed! ✖ float\double-dot-02.toml ✖ float\double-point-2.toml Completed: 529, Succeeded: 527, Failed: 2 I was expecting the same failures as in Delphi 11, but got two different ones.

When compiled with Delphi 11 3 of the tests fail: ✖ comment\after-literal-no-ws.toml: 'inf' is not a valid floating point value ✖ float\inf-and-nan.toml: 'nan' is not a valid floating point value ✖ spec-1.0.0\float-2.toml: 'inf' is not a valid floating point value Completed: 205, Succeeded: 202, Failed: 3 Completed: 529, Succeeded: 529, Failed: 0 ✓ All tests passed! No idea how to fix that. (On the other hand I am not that bothered because I don't really use Delphi 11 anyway.) I hope that feedback was useful for you. And thanks a lot for the effort you put into that library.

TJsonObjectReader was apparently introduced in Delphi 10.4 so I got a bit further and then hit the next error: [dcc32 Error] Tests.dpr(112): E2003 Undeclared identifier: 'Contains' That's TStrings.Contains which doesn't find. And that apparently was introduced in Delphi 12. But the reaplacement would be really simple: b := List.Contains(S) // becomes b := IndexOf(S) >= 0; And now it compiles.

No luck, now it's [dcc32 Error] TOML.Parser.pas(178): E2149 Class does not have a default property I added ".Items" in 4 places in that unit and then got [dcc32 Error] TOML.pas(130): E2003 Undeclared identifier: 'TJsonObjectReader' So I guess making it compatible with 10.2 would be quite a lot of effort (And I'm not even talking about Delphi 2007 which I would have tried next. 😉 )

The tests from files-toml_1.0.0 now all pass. Should those from files-toml_1.1.0 also pass? They don't: ✖ datetime\no-seconds.toml: Error at 2:26: Expected ":", got "EOL" ✖ inline-table\newline-comment.toml: Error at 5:2: Expected "ID", got "End of Line" ✖ inline-table\newline.toml: Error at 4:2: Expected "ID", got "End of Line" ✖ spec-1.1.0\common-12.toml: Error at 1:54: Invalid string escape char: "x" ✖ spec-1.1.0\common-29.toml: Error at 1:24: Expected ":", got "Z" ✖ spec-1.1.0\common-31.toml: Error at 1:24: Expected ":", got "EOL" ✖ spec-1.1.0\common-34.toml: Error at 1:12: Expected ":", got "EOL" ✖ spec-1.1.0\common-47.toml: Error at 5:5: Expected "ID", got "End of Line" ✖ string\escape-esc.toml: Error at 1:9: Invalid string escape char: "e" ✖ string\hex-escape.toml: Error at 3:21: Invalid string escape char: "x" Completed: 214, Succeeded: 204, Failed: 10 Completed: 524, Succeeded: 524, Failed: 0 ✓ All tests passed! But I guess that's because it's TOML v1.0.0 compliant, not v1.1.0. I also noticed that you removed the IsBufferValid call. I'll try to compile with Delphi 10.2 again.

Found it. I didn't know there was a submodule.