Lars Fosdal

Why won't this work with inline vars? Is it the ListBox.Items.Add that doesn't copy the Couple string?

For our apps, we use EL to capture the exception, then log them both to a local log file (debug out type) and to our database. As mentioned, it is timewise expensive, so we take care to not use exceptions for normal flow control.

It is at least interpreted correctly with regards to type and type size. 32-bit SizeOf(Type(1)) 1 Byte 1 UInt8 1 Int8 1 ShortInt 2 Word 2 Int16 2 UInt16 2 SmallInt 4 FixedInt 4 FixedUInt 4 Integer 4 Cardinal 4 NativeInt 4 NativeUInt 8 Int64 8 UInt64 64-bit SizeOf(Type(1)) 1 Byte 1 UInt8 1 Int8 1 ShortInt 2 Word 2 Int16 2 UInt16 2 SmallInt 4 FixedInt 4 FixedUInt 4 Integer 4 Cardinal 8 NativeInt 8 NativeUInt 8 Int64 8 UInt64 program TypeCastSizeOf; {$APPTYPE CONSOLE} {$R *.res} uses System.SysUtils; begin {$ifdef CPU32Bits} Write('32-bit'); {$else} Write('64-bit'); {$endif} Writeln(' SizeOf(Type(1))'); try try Writeln(SizeOf(Byte(1)),^I'Byte'); Writeln(SizeOf(UInt8(1)),^I'UInt8'); Writeln(SizeOf(Int8(1)),^I'Int8'); Writeln(SizeOf(ShortInt(1)),^I'ShortInt'); Writeln(SizeOf(Word(1)),^I'Word'); Writeln(SizeOf(Int16(1)),^I'Int16'); Writeln(SizeOf(UInt16(1)),^I'UInt16'); Writeln(SizeOf(SmallInt(1)),^I'SmallInt'); Writeln(SizeOf(FixedInt(1)),^I'FixedInt'); Writeln(SizeOf(FixedUInt(1)),^I'FixedUInt'); Writeln(SizeOf(Integer(1)),^I'Integer'); Writeln(SizeOf(Cardinal(1)),^I'Cardinal'); Writeln(SizeOf(NativeInt(1)),^I'NativeInt'); Writeln(SizeOf(NativeInt(1)),^I'NativeUInt'); Writeln(SizeOf(Int64(1)),^I'Int64'); Writeln(SizeOf(UInt64(1)),^I'UInt64'); except on E: Exception do Writeln(E.ClassName, ': ', E.Message); end; finally Readln; end; end.

This has been resolved.

@RDP1974 I deleted the edited empty post. Was that the one you wanted to remove?

If you need to produce executable code for MacOS and iOS - you need stuff that is NOT out-of-warranty, i.e. the Mx generation of CPUs. I built all my computers myself from 1984 until 2008. After that, it has been laptops and mini PCs. I bought an MBP M1 Pro when it came out, and it and later models using the Mx platform, cannot be upgraded. You have to pay the Apple tax on more memory and more storage.

Average consumers of hardware, then. Not all programmers tinker with hardware. And, if they bought a newer Apple device, they wouldn't typically be able to do so, as not all programmers are handy with soldering tools. Those of us that are, would probably be reluctant to void the warranty of their new devices.

Intel Macs are going the way of the Dodo. It is all about ARM for Apple now. The Apple Tax refers to the premium you pay if upgrading from the base spec of an Mx based device. The cost is ridiculous. You could buy a second device for the price of the upgrades. Edit: ...and your average consumer cannot upgrade the device by themselves.

I don't use the EL dialog nor do I capture screenshots. @Attila Kovacs But, in EL Options, under dialog: it looks like you can make screenshots mandatory? Disclaimer - I haven't tested it. Edit: Well, reading the docs says it doesn't work that way - and that there are GDPR pitfalls if not asking for consent. https://www.eurekalog.com/help/eurekalog/index.php?bug_report_screenshot.php

Same reasons that Anders mentioned. Also, Amazon has a brutal grip on the market, and is killing off the competition. For books, I've opted to pay more and order them from a local bookstore.

Normally, it would be by editing the first post. I modified the topic for you.

@RDP1974 Something like "New mem manager test using indy http, json, memtables, etc"

Does it always fail on the same parameter? I'd probably do it like this, but it depends on the declaration and description of the GetOptParameter method. var FNameOut: AnsiString; begin ... FNameOut := UTF8Encode(ParamName); if FDSBase.GetOptParameter(0, FieldNo, @FNameOut, ParamType, ...

@RDP1974 - Please change the title of the post to reflect the content - "new test" does not inform those that read the list of topics

These days I avoid shopping at Amazon. The new MacMinis look amazing - but yeah, the Apple Tax is brutal.