dummzeuch

For a while I put Word/LibreOfficeWriter and Excel/LibreOfficeCalc documents in subversion, but since they are binary it's pretty pointless, because one cannot easily find what changed. I put some configuration files (linux) there and of course source code of all kinds, including third party sources (and use these via svn:external).

I think you overestimate the complexity of an automated build: Have a release configuration in the IDE Build from command line. That's it. You can always add more to the automation but the command line build is a good starting gpoint.

I never heard that term either, but I'm not American. I heard of Fintech though, not sure what it means other than just another buzzword about making money with other people's money.

Is this the plain IDE or do you use some plugins?

Hm, but you are not @Quarks, so your reasons don't count in this context.

Why not using the Windows API CopyFileEx? As far as I know it has no size limitation. It also allows a callback for showing the progress and possibly cancelling the copy. If you need an example, have a look at TFileSystem.CopyFileWithProgress in my dzlib. Or am I misunderstanding your requirements?

Buffered file stream will get you no performance improvement in this case. It only has an advantage for reading and writing (many) small parts of a file, but you are using a buffer of 512 KBytes already.

a := muldiv(b,c,d); Of course, this is a function, not a ternary operator, but ... a := b * c div d; ... is not really *one* operator tut two, but neither is ... a = b?c:d; ... so does it qualify?

I just implemented some functionality using TCustomIniFile.ReadSubSections which depending on the type passed to it, either calls the TMemIniFile or the TRegistryIniFile method. Something like: procedure doSomething(_Ini: TCustomIniFile); var sl: TStringList; begin sl := TStringList.Create; try _Ini.ReadSubSections(sl) for i := 0 to sl.Count - 1 do begin doSomethingWith(sl[i]); end; finally FreeAndNil(sl) end; end; This works fine in Delphi 10.2 but not in Delphi 7 because TCustomIniFile.ReadSubSections didn't exist back then. I need that functionality for older Delphi versions, so I somehow must implement ReadSubSections there. Unfortunately the implementations differ greatly for TMemIniFile and TRegistryIniFile. I'd have to check which class is passed in and call the respective implementation. if _Ini is TMemIniFile then HandleMemIniFile(_Ini) else if _Ini is TRegistryIniFile then HandleRegistryIniFile(_Ini) else raise Exception.Create('Only TMemIniFile or TRegistryIniFile supported'); But this just feels very clunky. Is there any better way? (Just in case somebody wants to suggest them: Class helpers didn't exist in Delphi 7 either.)

Yes, but how could they help here?

Yes, but I would still have to use similar code as above to typecast to the correct class.

(I must be CompilerVersion < 14 because the method was introduced in Delphi 2010.) Unfortunately subclassing TMemIniFile and TRegistryIniFile wouldn't allow me to pass TCustomIniFile.

Actually that was how I understood the original question: But maybe I was wrong, happened before.

Actually, it might cause an enum to not have RTTI: "Enumerated constants with a specific value [...] do not have RTTI. (from http://docwiki.embarcadero.com/RADStudio/Sydney/en/Simple_Types_(Delphi)#Enumerated_Types_with_Explicitly_Assigned_Ordinality ) (I didn't check this.)

Exactly. Changing working code just because it can now be written differently, is not a good reason in itself. I wouldn't refactor code only to now use inline variable declarations either. But if I have to refactor it for other reasons, I might consider it (same for custom managed records, but I'm not yet sure I trust the implementation).

We could probably improve this with a try ... finally and exceptions. 😉 (I actually have some code that does this because a coworker complained loudly about the gotos I was originally using.) Let's create a new thread with worse "improvements" ("Verschlimmbesserung") for this code.

+1 for goto! 😉

Why should I? Existing code just works as it is and unless there is a good reason to change it, I won't touch it.

Note though that this kind of enums has only limited support in RTTI. btw: This has been available since Delphi 6, so you are rather late to the party. 😉

My all time favorite: if SomeErrorCondition then Exception.Create('Errormessage goes here'); (raise is missing, just in case you didn't notice.) Or alternatively: raise exception('SomeErrorMessage'); (create is missing) Makes for a "nice" Access Violation in the exception handler. Both were in my own code, but the first one was also in some older RTL and JVCL and Indy code (all fixed now). I blogged about this a while ago. (OMG, back then we still hat Google+ !)

If you only need thumbnails, why not explicitly scale your picture to a bitmap of whatever size you need and cache that? Of course that takes time.

To get the size of a memory stream, add InstanceSize and Capacity. Unfortunately capacity is usually larger than the actual size of the data and of I remember correctly, TMemoryStream does not allow setting the capacity beforehand. But you can easily add that functionality. I think I've got such a class in my dzlib. Setting the size also sets the capacity, so If you know the expected size beforehand, set it first before writing to the stream to avoid allocating more memory than necessary. I have no idea how to calculate the memory used by a TJpegImage. If you want better performance, don't use TJpegImage for decoding but LibJpeg-turbo. I haven't measured it, but subjectively the difference is staggering.

The Uses Clause Manager in GExperts has an “Identifier” tab that can be used instead of the Find Unit refactoring of the Delphi IDE (which for me doesn’t work most of the time and if it does is very slow). And of course the Uses Clause Manager also works for older Delphi versions which simply didn’t have this refactoring. For this to work it parses all source files in the various search paths of the project. And because this takes a while it caches the results and only updates this cache if a new unit is found or a unit has been changed. read on in the blog post

The Rename Components expert in GExperts now has separate lists for the names and additional properties for VCL and FMX components. Previously it was a hassle to have additional properties shown in the rename dialog if these have different names in VCL vs. FMX e.g. the Caption vs. Text property of TLabel. Now you simply configure them differently. read on in the blog post.

That's not GExperts specific. Every major Windows update breaks the Delphi 2007 installation in this way. I blogged about this issue a few years ago: Delphi 2007 on Windows 8.1 And I'm always glad I did, because I tend to forget how to fix it. Thinking about it now, I wonder if I shouldn't simply add those 4 files to my build tools and change the build script to have the environment variable point there.