Vandrovnik

EPNGOutMemory - may be the reasons is just in the number of simultaneously opened forms (which contains big images)? In that case, 64-bit IDE would solve the problem. I keep open just a few forms and datamodules, may be that is the reason why I have never encountered this problem.

So old bugs will be converted to C++ and new bugs will appear from the conversion itself 🙂

At least 128-bit IDE 😉

Just curious - please could you post a screen shot of the error message, when you encounter low memory in the IDE?

Multiline strings!

I wonder what is the reason that we have so different user experience with IDE. Maybe third party components? Some IDE wizards/experts? Or you are using a part of Delphi language, which I do not use, such as types defined inside a class, inline variables etc.? For debugging, I compile to 32bit, because 64bit debugger was very slow and I do not check with each new IDE version, whether it is already better.

For me, code completition works almost always fine in Delphi 11.3.1 Pro. Project size is over 1 000 000 lines of code.

It probably treats that section as published then: The compiler treats a published section like public unless RTTI is enabled with the $M or $TypeInfo compiler directives, or if the class inherits from a class with RTTI enabled. TPersistent in Delphi’s Classes unit enables published RTTI, so all persistent classes (including all components, controls, and forms) have RTTI. The initial, unnamed section is published for classes with RTTI.

What error message do you get?

But it does not change internal layout, does it? Just the address of code, data and stack segments is randomized.

Why? Can this be a problem for a correctly written application?

Eh, sorry, I have seen UInt16 in parameter definition and did not notice that temporary variable is Int16, without the "U"...

For input = 0, I would expect the problem already here: Dec(TempInt, 2048);

destructor Destroy; override;

That will loop the code (x+1) times 🙂