David Heffernan

This is incorrect. Changing font properties in an event handler is fine.

It has nothing to do with assignment. It's pretty rare for absolute to be useful. Pretend it doesn't exists, and you'll get a long way.

It will never find invalid pointers, but that's not why Assigned exists

I think the use of string here is to allow encoding of indeterminate masses for elements with no stable isotopes, or something along those lines. Look at the items with mass surrounded by parens.

What are you trying to achieve here? As Stefan says, why aren't you declaring these as records to begin with? And why would you want to make anything here a variable. Seems like this area of Physics is pretty much fixed!

It's the official name for them, as you can see from the documentation https://docwiki.embarcadero.com/RADStudio/en/Anonymous_Methods_in_Delphi

We've no idea what your system is. There are many versions of Delphi. We don't know what your app manifest is. These are both possibly relevant.

Whether or not you want to use asm is not relevant. It's what you do with it that matters. I mean, exactly what you said above would apply equally if you wanted to write the code in pascal.

Why would [ref] be needed to use asm?

Is there any known use case other than the one demonstrated by FreeAndNil, namely to allow modification of a const param?

Is there any known use case other than the one demonstrated by FreeAndNil, namely to allow modification of a const param?

McAfee, like so many AV products, the cure is worse than the disease.

Isn't this a well documented file system for which there are multiple open source projects that you can use to support the documentation? More generally, I'd advise you to put more effort into asking questions. Time spent describing what your problem is, what you already know, where you are blocked, etc. is effort you should spend if you want to get something in return.

Doesn't sound like it's not that exceptions aren't handled. App exiting is entirely different. How about the details we asked for.

Or maybe floating point exceptions are masked so there is no exception. We can't see your code, or know what version you use.

That makes a lot more sense. Assumed it was common knowledge? I'm not so sure. I think there's still a big underbelly of Delphi coders that don't get this.

My point is that it's behaviour that you don't ever need to know because the correct way to handle byte data is as, well, bytes and not text. So for sure there's an algorithm, but it's not one that anyone actually needs to know.

This way is reliable and works

I mean, you work with strings and do TEncoding.ASCII.GetBytes

I don't see this as helpful to anyone. Use bytes to represent bytes. Use strings to represent text. Don't use ANSI strings.

What is wrong with the world of Delphi programmers that in 2025 there are still people who can't understand the difference between text and bytes? The article you link to goes on and on about text but your data is bytes. Why not just use the correct data type?

Now we are discussing what the cheap and rubbish version of ChatGPT says about Delphi?

Then please provide a complete but minimal reproduction.

This is just a debugger issue, you shouldn't change your code because of this

The best piece of advice you can take from here is that you need to learn how to ask questions effectively. Because if you ask like this then nobody can help you. And it's just a waste of your time.