David Heffernan

Signing would help

I've never in my life seen it written like that. Sure it works. But when you read it, it's not familiar and so it makes you think about it. Impedence. Patterns matter.

What's especially awesome about the VCL code is that it writes the for loop in a really weird way as for var I: Integer := 0 to -1 + Items.Count do with the -1 before the count, and that seems to have taken from Setting the drop down width of a Combobox in Delphi – twm's blog (dummzeuch.de) which in turn is taken from Sizing the ComboBox Drop Down Width (thoughtco.com)

I think the asker knows this. The question though is how many variables are there for an inline var inside a loop. Is there one variable? Or is the N variables where N is the number of times the loop body executes? That's the question being asked as I understand it. The answer is that there is one variable. Seems like this is the opposite behaviour from C# https://stackoverflow.com/q/271440/505088 Personally I feel like Delphi has a poor design choice here. I'd expect a local variable that is defined inside a scope, to have a lifetime that was that scope. With the C# design you can achieve both possible behaviours by defining the variable inside or outside the loop body. In Delphi you have to resort to putting the body in a separate procedure. The we have C++ which allow capture by value or variable as specified by the programmer in code. That would also give the same flexibility but without requiring extraction to separate procedure. Or am I wrong? I'm basing this on reading and not practical experience so I may have misunderstood.

Use the 32 bit debugger

If you can distribute one file you can distribute more than one. This always feels like a pointless discussion. Solving a problem that doesn't exist.

Usually each release comes with a bunch of bugs fixed, and a new set of bugs released into the wild. I do think the product is slowly getting better though.

Do they treat you differently when you answer?

Who cares about TIOBE? It's just irrelevant.

It's strange that if this is what you want that you ask for something else. Classic XY problem.

Address space fragmentation and sub allocation fragmentation.

Love the engagement here from the poster

Yes, but what is reporting the memory leak? There are lots of leak detection tools. If you use full fastmm then you can get allocation stack traces. It doesn't sound like you've really understood the issue. Normally Text would just map directly to GetText. But we still have no idea what Value is. This thread displays a deeper problem. That you think we can tell you what is happening with such incomplete details highlights the fact that you are also trying to solve the problem without those details.

We can't guess what the code is. We still don't know how you are detecting.

We've no idea what Value is. How are you detecting that there's a leak.

Is the debugging experience still terrible though?

How are you detecting that the memory has been leaked?

"Material is not a valid floating point value" Ask yourself why you are trying to convert the text Material to a numeric value. Do you know why yet??

This seems extremely optimistic

Set a break point on the line where the error occurs. When the code breaks there inspect the value of the argument passed to StrToCur.

Find a tutorial on how yo use a debugger

The error message seems quite clear. Do you know how to use the debugger to inspect vakues being passed to StrToCurr?

But is anybody going to get paid and have any job security?

It would really help if we could down vote issues as well as up vote them

This post here isn't going to have any impact