Lars Fosdal

There are virtual rent-a-mac services around. https://www.macincloud.com/

Did any of you ever try Alice Pascal? Fascinating syntax enforcing IDE from the same era. https://www.templetons.com/brad/alice.html

Me too, @luebbe. My first Pascal was Compas Pascal on Z80 - which transmogrified into Turbo Pascal for DOS and CP/M. ... checks himself for lichen and moss growth again...

You could do a fixup on the forms at runtime for Sydney, enumerating the controls on the forms/frames and set TLabel.Transparent to false? Do the frames have a common ancestor?

Register here https://blogs.embarcadero.com/whats-coming-in-10-4-2-sydney/

This means I now have 26 years of experience with Delphi, and I still feel like a n00b around parts of it.

@Marco Cantu - See the above comment. Surely we can't solve CE license issues at Delphi-Praxis?

Please use Embarcadero's online support for registration and installation issues. https://www.embarcadero.com/support

If the first thing I do is to set a local variable to a specific value - any previous initialization would be wasted. Managed vars are a different story - since approaching an arbitrary pointer would be unfortunate.

It would be for Sydney that it is most interesting to report, me thinks.

Slightly worrysome that there was no warning. Is it complicated to reproduce it and report it?

The check has a performance penalty, so using assert is probably the better option if you must have verification.

@Marat1961 According to your link So, by the general rule is not required, as the caller is responsible.

You can have an example repository with several sub-projects in their own folders. Each example would be a self contained project, ready to download, compile and run. Doing fixes would be easy. Adding features would be easy. Taking contributions would be possible.

Correct. Which ones that one can trust to be. Which ones that can be made to be - and how. The impossible ones. Perhaps even a set of cookbook examples on how to do atomic exchange of different variable types, and what to do if you can't do them atomically due to misalignment.

Someone should author the definitive article on the memory alignment of variables. Which ones always are? Which ones may not be, and how to fix it? Which ones, if any, are out of your control?

Would it not be nice if the whole thing was on GitHub, GitLab, BitBucket or similar where it could be easily shared and modified, instead of a wall of code on a forum?

Ordered ePub + Paper.

That protocol looks more like a Serial cable protocol, than a TCP protocol? What happens if you send it as binary bytes instead of text hex? I.e. each hex value converted to a byte.

Nice, Carlo. I use the SVG preview capability from https://docs.microsoft.com/en-us/windows/powertoys/file-explorer

Scoping can lead to some weird scenarios. F.x. type TBase = class private public Data: Integer; end; TChild = class(TBase) private public Data: string; end; But, being able to "hijack" methods, simply by introducing them to the visible scope, is also kinda useful. A set of hints would be nice, though, so that you don't do it by accident.

Nothing beats pointers to arrays for InterOp - even today.

By "need to pass it to a (read only) memory area" - what do you actually mean? Do you want to get data from aData or put it to aData? Edit: ok, I read that again. What you want to do, is to allocate your TBytes array instead of using GetMem. SetLength(MyData, Size); Whatever fills your GetMem block, should also be able to fill @MyData[0] with the length you have preallocated? You then pass that as Something(MyData);

Here is how our TIdTCPServer shutdown code looks. That exception doesn't really happen anymore, though. 🙂

Ah - Brain fog cleared. Thanks, guys.