David Heffernan

Not sure I agree. It can be useful to distinguish between null and length 0 array. It can be useful to have these as different conceptual things.

Well in the case of structured storage, it's an old legacy technology that won't change. So does it matter that your library isn't actively maintained?

It's Java. Very early on many C# programs were also valid Java programs.

That's not really why byte is useful. Byte is primarily useful to store binary data, typically as TArray<Byte>. It's rare to use Byte to store a count for example.

No there is not. However, you really should not be using short strings at all. These only exist for backwards compatibility with legacy code.

I don't understand the question. Obviously the code here is not valid. Can you describe what you want to achieve.

I remember working with the ExpressSpreadsheet xls code which is based on BIFF records and COM structured storage. The developers had implemented a lot of code to handle the structured storage side of it all, and whilst it mostly worked, there were a couple of obscure bugs which were flushed out by writing huge files. After spending some time debugging it all, we threw away all of the third party code that implemented structured storage and replaced it with the system provided COM objects. So I guess what I am saying is that the approach outlined by @Alexander Elagin above seems likely to be good advice to me.

This has always been a total heap of crap

Ah, yes, I see now! Wise

It's Python. Perl's conditional operator is the same as C. That looks completely different. And has the condition first. Quote unlike how it is done in Python.

I don't think that rings true. I mean the Python if statement is the same as the Pascal if statement. The Python syntax is closer to natural language than what is done in Oxygene. I don't see either as being particularly in keeping with Pascal, one way or another.

He's already using SourceTree which displays the information......

I don't understand most of the answers. Mike wants to see the information in the RAD Studio IDE.

This entire thread is largely pointless because we don't have a clear idea what you are trying to do and what your code looks like.

So write it in Python.

Why don't you write something yourself to do this?

I watched the sneak peak webinar and Marco mentioned that apps would no longer run on XP and also described the workaround in the original post here. So yes, this is intentional, and submitting a QP report would be kind of pointless. However, if you want there to be one you could do it yourself, rather than ask somebody else to do it.

They explicitly don't want to keep on supporting these old versions. Why? Emba have done all this intentionally.

Does GExperts and/or the IDE that you are using support per monitor DPI?

I wonder if the x64 windows debugger works now

Why is nobody else reporting this issue?

Irrelevant. Good products are cohesive. Different aspects work with each other and support each other. Funny. Binary literals, digit separators and avx512 asm. That's the entirety of new language features. That's a pace that can only be described as glacial. Cant be hard to get the old formatter to work. If it's an arse for them to do it, tough. Their adult for building up so much technical debt. Honestly, look at the quality of what comes out of Emba and compare to other mainstream IDEs.

Honestly you'd think they'd have got the memo by now!!! What is wrong with them?!!

These are nice features but they are also completely trivial.

Do mean decimal seps or thousands seps?