Leaderboard

@Fr0sT.Brutal If you have nothing substantial to contribute to a users topic please refrain from posting.

According to the 80/20 rule, whereas 80% of the work can be finished in 20% of the time, you actually have spent 15% of the time needed to get 100% of the work done

The purpose of a class constructor is to initialize the class to a known initial state when it's created. Imagine having to different ways to start your car if you were alone or if you had passengers, just so the system that supports airbags knows whether to only activate the Driver's-side airbag or all of them. Airbag activation based on secondary properties that can't be known until run-time (ie, how many people get into the car) is not part of the object's "initial state". FIRST you start the car. THEN you do other things like activate the airbags. You do NOT want to have different ways of starting the car based on factors that depend upon secondary systems. It doesn't need to be airbags -- it could be A/C vs. Heater; driving in the day vs. at night where lights are required; etc. Creating your objects is like starting the car and getting the engine running. C++ and C# (among others) have a way to inject initial state data into constructors at the time of declaration vs. run-time. Delphi doesn't have that ability, so you need to inject the really core initial parameters in the Create call, and then add others AFTER the object has been initialized via property injection.

The ifdef is pointless and wasteless. On x64 stdcall is, like all calling conventions, ignored. So remove the ifdef and leave stdcall there for the platform that it has meaning.

Unlike in 32bit, multiple calling conventions simply do not exist in 64bit. There is only 1 calling convention, and it is dictated by the 64bit ABI itself. Keywords like 'cdecl' and 'stdcall' are ignored when compiling for 64bit, so as not to break code that is being ported from 32bit.

Thanks for all the feedback! Single constructor Create from now on 🙂

And... RSP-27358 is back open again. Minor victory! Thanks Bruneau Babet and those that commented on this and https://quality.embarcadero.com/browse/RSP-27412

@TomDevOps There have been some corner cases, but I think most of them have already been fixed (for ex. https://quality.embarcadero.com/browse/RSP-23417) or will be fixed in 10.4.

We have just released v6.12 of our suite of components and routines for Embarcadero Delphi - ESBPCS for VCL - this is a free upgrade for registered owners. ESBPCS for VCL supports Embarcadero Delphi 10.3 Rio all the way back to Delphi 7. This release includes an important update for Date Edits, as well as updates to the Calculator Engine and more Measurement Conversions. Trial versions and Demos can be grabbed from https://esbconsult.com/esbpcs/downloads.htm

They could create method with correct name and for some time keep the bad one in place too, just marked as deprecated... Just if there were a will to fix things.

Also a false goal.

That's a false goal. Remove that goal from your life. Following it will be making your code worse.

Well, I am sure you will understand that it's not really nice to advertise another product in a thread specifically presenting HxD. I have invested many years into it (since 2002), and it has been Freeware all the time. A little respect for that effort would be appreciated.

I FINALLY got it! Your posts with sudden UPPERCASES remind me balloons in comics. You should use proper comic FONT as well xD