A.M. Hoornweg

I'll do that (create the QP), thank you. (edit) https://quality.embarcadero.com/browse/RSP-33241

To each his own. For single-exe projects it is a non-issue and I wouldn't bother either if my project consisted of only a handful of modules.

I haven't ported the project group from XE to Sydney yet, for now the directive is needed for XE where it applies to all units that the compiler rebuilds. I just wish Embarcadero had optimized RTTI for size from the very beginning and given us the choice wether to use it at all. Having RTTI in your code offers possible attack vectors for reverse engineering etc.

I use a RTTI-stripped version of the XE libraries since ages, because when I migrated from Delphi 2009 to XE my executable sizes also grew a lot. That RTTI stripping is much easier to achieve with XE because the {$RTTI....} directive was still a global option then, so you don't need to patch any source files. Stripping RTTI is now an integral part in my Finalbuilder build scripts. Edit: I have attached an image with the executable sizes. All executables were compiled in "release mode" without any debugging info. All executables were compiled with {$WEAKLINKRTTI ON} and {$RTTI EXPLICIT METHODS([]) PROPERTIES([]) FIELDS([])} in the DPR. (1) Compiled with XE10.4.2 Sydney. (2) As (1), replaced unit "Oleserver" with a dummy unit so no unnecessary VCL code is pulled in. (3) As (2), using a RTTI-Stripped RTL/VCL. (4) Compiled with Delphi XE, replaced unit "Oleserver" with a dummy unit so no unnecessary VCL code is pulled in. (5) As (4), using a RTTI-Stripped RTL/VCL.

The purpose of a spinlock is to obtain the lock as quickly as possible. On a single core system, doLock should yield on contention because the thread that owns the lock is waiting to be resumed. On multi-core systems it can keep spinning. In the initialization of the unit, call GetProcessAffinityMask() and count the bits in the integer to obtain the number of cores available to the program.

One problem I see is that on a single-core CPU, doLock will burn up all remaining CPU time of the time slice on contention.

Hello all, I see that Delphi supports both bitwise and logical versions of and/or/xor operator overloading, but I'm not 100% sure about the difference between the two concepts. Assume I have a certain record type, and that I want to implement "AND", "OR" and "XOR" operators, each resulting in some kind of merge of the original input records. The syntax I would like to use in my code would simply be "A:=(B OR C);" Do I need to implement BitWiseOr etc or LogicalOr, and if I implement both, how does Delphi decide which of the two is going to be used?

I did consult the wiki but somehow managed to skip this line of text ten times. It must be monday morning .... Thanks for pointing it out!

Hello all, is there a way to quickly initialize all local variables of a procedure with zero, maybe using FillChar? It would be very practical to use at the beginning of a procedure. I had a case recently where the Delphi compiler didn't throw a warning when I accessed a local variable before it had been initialized and it had me debugging for hours.

Generally, yes. But it would also be great to have a nifty tool at my disposal that lets me wipe all locals on the stack with a single call, especially if it is a complex routine with lots and lots of local vars. In such cases it would simply save a lot of boilerplate code. Delphi does the very same thing for class members and I would totally hate it if it didn't. I had hoped that this would be a trivial thing to write, since all StdCall procedures start with a byte sequence like "mov ebp,esp; add esp, -sizeof(localvars)".

Normally yes. I only asked because I overlooked initializing a certain local variable and the compiler (Delphi XE, which is used in that specific project) didn't warn me. OTOH, if Delphi takes the trouble to zero-fill managed local variables anyway, it puzzles me why it does not simply fill the rest as well. A REP STOSD is lightning fast.

It seems to vary with compiler versions. I use both XE and Sydney.

Can you use the postal code to identify the town and street? In the Netherlands we have a system where the postal code combined with the house nr uniquely identifies an address. For example, enter "Netherlands 2594 BD 10" in google Maps and you'll see where our king lives.

The reason is, that when S goes out of scope, it decrements the reference count of G. G should only be destroyed when its reference count reaches zero so that action must be atomic.

That may very well be true. But when a developer is doing refactoring to make code more legible and concise, IMHO it is a good thing if the parameter list reflects the intended use of the parameters. So if a parameter is intended just for outputting something and not for modifying an existing value, the "out" modifier is clearer than "var". I find "const" parameters confusing at times, especially when passing stuff like arrays. If I pass an array as a const, am I supposed to be able to modify elements or not? The Delphi documentation (link at he bottom) says "... constant parameters are similar to value parameters, except that you cannot assign a value to a constant parameter within the body of a procedure or function..." . I don't want to nit-pick, but I find it very confusing and counter-intuitive that I can modify the array in such a case. Type tintarray=tarray<integer>; Procedure dosomething (CONST a:tintarray); var i:integer; begin for i:=0 to high(a)-1 do a[i]:=random(maxint); end; procedure TForm1.Button1Click(Sender: TObject); var x:tintarray; begin setlength(x,10); //newly allocated space is set to 0 dosomething(x); showmessage(format('%d',[x[0]])); end; http://docwiki.embarcadero.com/RADStudio/Sydney/en/Parameters_(Delphi)#Constant_Parameters

Unlike "shortstring", Delphi cannot pass managed types such as strings by value. It is always a pointer. I'm not 100% sure but I think an "out" parameter is like a "promise" to return a value no matter what, and also a promise not to use it for input. The problem being that it is possible to pass the same variable twice and thus circumvent the no-input promise.

"Out" parameters of managed types (such as strings, interfaces, dynamic arrays) are initialized before a method is called. The problem only arises because multiple parameters in the method reference the same string. The behavior is correct but very counter-intuitive. It would behave more intuitively if the compiler would issue a UniqueString() for the second/identical parameter.

I posted about it before in this forum and was told that it's intended behavior. Admittedly, it's a corner case, but it did happen and cost me a lot of time to figure it out. A compiler warning would have been nice.

There's also this thingy called "tGridpanel" in Delphi. I have never used it myself though.

How about metadata (access rights) , triggers etc?

"Out" parameters are an even bigger can of worms. I had refactored some code recently to use "OUT" parameters instead of VAR parameters (in order to more clearly document the intended use) and it had side effects that were hard to figure out. I thought my debugger had gone bananas. Try single-stepping through this code and watch the values. In hindsight, the cause is clear, but I find the compiler should throw a warning if it encounters such a situation. I now avoid OUT parameters. procedure tform2.test(OUT somestring:String; Defaultvalue:String); begin Somestring:=Defaultvalue; end; procedure TForm2.Button1Click(Sender: TObject); var t:string; begin t:='Testing 1-2-3'; Test(t,t); Showmessage(t); end;

TMS FixInsight (a sourcecode analysis tool) flags non-const string parameters as bad practice if these strings are never written to.

Did you install any software or packages recently that changed your system's "path" variable? The Windows PATH variable has a limited maximum length. If setup routines keep adding entries to it then it may get truncated and all sorts of things on your system stop working properly. Like Delphi not finding its installed BPL's anymore. Happens to me all the time. Some component manufacturers (like TMS) store BPL's in non-standard locations and that regularly causes me headaches for this reason. I really wish component manufacturers would stop doing that.

My current approach is to store all *.PNG files in high resolution inside the resources. I scale them down to the appropriate size when the application starts and the display resolution is known. I use my own scaling routines (using a Lanczos2 filter) but there are lots of libraries that can do the same thing. This approach does not solve the situation of the user having multiple screens in multiple resolutions though.

@emailx45 you're kinda missing the point. Decoding is not the issue here. My point is that a "month" does not have a constant value. So expressing a countdown as "2 months and 5 days left until..." is totally vague. If there is a distance of 29 days between two dates, that distance can be either exactly one month, one month plus a day, one month minus a day or one month minus two days, depending on where in the calendar you are.