Uwe Raabe

If you can provide reproducible test cases, you should send them to Peganza. They are always interested in cleaning out those glitches.

Well, that would require some sort of compilation or so and is definitely outside the scope of such a tool. It might be worth to investigate in interpreting the output of Peganza Pascal Analyzer Uses Report and act accordingly. This would eliminate the burden of analyzing the code.

Set Compressed=0 See above.

It may help to place that directive in the project file instead of the unit with the class declaration.

@sLesage This is an early beta. It is a command line tool called with the following parameters: UsesCleaner [<filepath>]<filename> [-c:<configfile>] [-o:<outputpath>] [-l:<logfile>] [-s] <filename> may contain wildcards <configfile> default is UsesCleaner.cfg <outputpath> if not specified, original files will be changed! -s: also handles subfolders The example config file is targeting Delphi 10.2 Tokyo, but can easily be adjusted. Some entries are self-explaining. [Settings] Indentation=2 Compressed=1 MaxLineLength=130 SearchPath=c:\program files (x86)\embarcadero\studio\19.0\lib\Win32\release; UnitAliases=WinTypes=Winapi.Windows;WinProcs=Winapi.Windows;DbiTypes=BDE;DbiProcs=BDE;DbiErrs=BDE; UnitScopeNames=Winapi;System.Win;Data.Win;Datasnap.Win;Web.Win;Soap.Win;Xml.Win;System;Xml;Data;Datasnap;Bde;Web;Soap;Vcl;Vcl.Imaging;Vcl.Touch;Vcl.Samples;Vcl.Shell GroupNames=@DelphiOTA;Winapi;System.Win;System;Data;FireDAC;Vcl;Rz* [Groups] DelphiOTA=ToolsAPI;DesignIntf;DesignEditors The tool will resolve any unit aliases and unit scope names. Then it will group the units according to the order given in GroupNames followed by any remaining units. Plain group names are taken as namespace prefix (like Data or Vcl). Unit names without such namespace can be grouped with wildcards (like Rz* for Raize Components units). You can define groups by simply listing the unit names in the Groups section as it is show with the DelphiOTA group. UsesCleaner.zip

Can you elaborate that statement a bit? What does better mean in this context? I never have had problems with backups of those files. It may take a while to copy them, but that is almost the same with multiple files.

Honestly, I don't know! I have all my virtual machines on a couple of SSDs and I don't see any performance drop compared to a host installation. It may have an impact for mechanical drives, but I never did some meaningful performance tests (which I expect to be difficult to do anyway).

That is the same in VMware - one file per virtual disk. Each virtual disk has a setting where you can decide if the disk shall be split into several files or just one. The default is split, but I prefer it the other way.

That is the first setting I am changing for a new VM.

What files are you referring to? Perhaps I have a different meaning for plethora.

Indeed ,NET has something called InAttribute and OutAttribute. AFAIK, there is no corresponding thing in Delphi.

You should even be able to just add the library using the Add button of the import wizard.

Build 2352 can be used with Delphi 10.3 and 10.3.1 again. If you have Delphi 10.3.2 you need to install the Runtime Packages Compatibility Patch first.

I decided to revert the build server to Rio 10.3.1, so future builds will be compatible with all Rio versions. For users on 10.3.2 it is mandatory to install the Runtime Compatility Patch then. A new build is expected for later this day.

@John Kouraklis That is mentioned in the text of the beta download page: