Vandrovnik

If log level is defined in compile time, he could also use $IFDEF or $IF instead 😄

In a loop, I would store the result of CanLog to a local boolean variable and then use "if StoredValueOfCanLog>=..." and direct call to your Log procedure (without anonymous function).

I tried to "vote" by adding a comment. And created a request for adding a "vote" button 🙂 https://embt.atlassian.net/servicedesk/customer/portal/1/RSS-1439

May be something like this, but it looks even more complicated then the test with if CanLog... 😄 type tLogFunction = reference to function: string; procedure Log(aLevel: integer; aGetLogText: tLogFunction); var s: string; begin if aLevel>1 then begin s:=aGetLogText; writeln(s); end; end; ... Log(0, function:string begin result:='abc ' + IntToStr(random(100)); end); Log(2, function:string begin result:='efg ' + IntToStr(random(100)); end);

Since 2021 😄 A busy man...

Thank you!

Please is there documentation for Indy? I tried to download it from https://www.indyproject.org/documentation/ , but all links are broken... (at least here they apper broken).

The new unit order can have unintended side effects - if two unites define procedures with the same names and their order is swapped, the code will use a different procedure than before (such as System.Math and Neslib.FastMath do).

When I change System.SysConst.pas or Vcl.Consts.pas (to translate some messages), I always put them to the folder where my app is and I also use Project, Add and manually add them. But I always keep the interface part the same as in original file, otherwise all dependent units have to be recompiled.

I hope they keep it the way it is - can you imagine how many broken versions we would have to suffer if they now moved .bpls to another process? 🙂

Reported 5 years ago 😞

Almost all my problems with JCL and JVCL installs were because of I had somewhere on the disk (on the path) another instance of JCL/JVCL, which was (partially) used instead of the new version.

I guess you cannot.

What about this: SELECT rdb$get_context('SYSTEM', 'ENGINE_VERSION') as version from rdb$database;

You can use instsvc.exe and run all of them as service simultaneously. When using instsvc.exe, use "-n" and create unique names for them.