David Heffernan

What does the documentation say?

I'd still see all the replies. It's an interesting topic that you raised but it needs a clearer example to bring out the issue.

The subject is dynamic arrays and not open arrays.

Whatever. The text in the blog post didn't make the types clear. I wasn't about to download some project from a file sharing site. It's quite easy to make a complete program in a simple console app. There must be a few posts on this topic out there already.

If we have no knowledge of the types involved in this code then for sure we can't know what's wrong with it.

Nothing in that that suggests there is a need for a global variable.

You claim that these global variables "need to be global". Why is that? It would not surprise me if it turned out not to be the case.

Yeah, seriously you should remove this. As far as the question, I guess you need to decide on exactly what you want to implement. Security concerns are seldom as easy as "just add a signature". You see a lot of people who want to implement security without a solid understanding and it usually ends badly.

What is Acrobat doing there? Is it a certificate is the security sense, or is it just an image? Now that we have your signature in the image in this post, can't we sign things and pretend to be you? If I steal your cheque book, can't I sign them now as you?

Methods aren't normal functions by that argument, so why are open array parameters fine for them? The real problem here is the decision to allow literals to have type determined by context. So [10] is either a set or an array. That is incompatible with other language features. Like method and operator overloading. There is a good reason why other languages don't attempt to infer type of literals from context.

In this circumstance, for testing equality, why do you believe that a function is better than an operator?

It feels wrong isn't much of an argument. If open array arguments are fine for functions why not for operators, which are just functions with syntactic sugar. Can you explain your objection with reason, rather than relying on what it feels like. And surely you understand why operators are often preferred to functions.

Operators are functions. There are certainly times when it might be useful to use arrays as operator arguments. I regret that the language designers have allowed literals to have meaning determined by context in various places. When there is insufficient context, as is inevitably the case on occasion, these kind of problems arise.

The design error is converting left button up into click. That's what Sertac said. Read his comment carefully. A click is button down, capture, button up.

This was already covered on SO https://stackoverflow.com/questions/54401270/when-i-perform-the-ondblclick-event-form1-to-open-form2-it-fires-the-oncellcl If you are going to cross post, please note the other places that you posted so that people don't duplicate work.

Doesn't sound like resource exhaustion is to blame. More likely plain defects in your code.

You don't need to keep forms alive to preserve settings because you don't store setting in form instances. You store them elsewhere.

It's not about the memory. It's about removing global variables that allow form instances to poke at each other's internals. It's analogous to making fields private rather than public.  Those form variables only exist because in Delphi 1 the designers were trying to ape functionality of VB.

The entire design seems wrong. Don't use a global variable for each form. Remove them. Use a local variable and destroy it when ShowModal returns.

But this topic concerns the 8 bits in a byte.

Who says that the variation isn't happening in your process?

You'll see similar results as you do presently I predict.

Ugh, a class allocated on dynamic memory just to do bit twiddling. What is so hard about the and operator?

Doesn't seem like a massive amount of variability. Probably depends on what your code does. You are measuring what is known as wall clock time. Total elapsed time. Why would you want to measure anything else? Wall clock time is the time as perceived by the users.

Define "pixel perfect" please