Lars Fosdal

@ioan - Do you have a more descriptive name in the version resource?

[dcc32 Warning] W1029 Duplicate constructor 'MyClassName.ConstructorName' with identical parameters will be inacessible from C++ {$WARN DUPLICATE_CTOR_DTOR OFF} does not seem to have any effect in Delphi 10.3.1 I know I can add an extra dummy parameter to change the signature - but shouldn't that $WARN thing have worked too?

Do you expect people to Google it? When asking questions, the quality of the question will affect the quality of the answers.

Using a queue is a healthy principle.

Because I'm most likely adding forms to the app and want to keep the uses list changes, but not keep the changes to the auto-creates, which may have seriously modified the startup code. Ideal? No. Pragmatic? Yes. A quick cut&paste.

At least not at 16x16 or 32x32 and 48x48 resolutions, above that it's often good enough.

True that hand-editing the .dpr file is a chance game. To the point that I sometimes keep the code in a separate comment block so that I can quickly restore what the IDE screwed up. But having two forms auto created isn't the problem in that context.

You'd be surprised of the amount of SVG icons that can be found. https://www.flaticon.com/

Well, I could create it explicitly, but it would be practically the same code?

Describing how to circumvent license limitations, or pointing to information about the same, is not acceptable within these forums. Thread carefully.

The only two forms I auto create is a login form and the main form. All dialogs, as well as all frames on the main form, are created dynamically based on user input. Never used? Never created.

What happens on Android, MacOS or iOS? Those are also LLVM compilers.

Eval looks ok on Windows. and your added e191 test writes a yes

You should register a QP, unless there already is one.

program LargeEnumSet; {$APPTYPE CONSOLE} {$R *.res} uses System.SysUtils; type TLargeEnum = ( e000, e001, e002, e003, e004, e005, e006, e007, e008, e009, e010, e011, e012, e013, e014, e015, e016, e017, e018, e019, e020, e021, e022, e023, e024, e025, e026, e027, e028, e029, e030, e031, e032, e033, e034, e035, e036, e037, e038, e039, e040, e041, e042, e043, e044, e045, e046, e047, e048, e049, e050, e051, e052, e053, e054, e055, e056, e057, e058, e059, e060, e061, e062, e063, e064, e065, e066, e067, e068, e069, e070, e071, e072, e073, e074, e075, e076, e077, e078, e079, e080, e081, e082, e083, e084, e085, e086, e087, e088, e089, e090, e091, e092, e093, e094, e095, e096, e097, e098, e099, e100, e101, e102, e103, e104, e105, e106, e107, e108, e109, e110, e111, e112, e113, e114, e115, e116, e117, e118, e119, e120, e121, e122, e123, e124, e125, e126, e127, e128, e129, e130, e131, e132, e133, e134, e135, e136, e137, e138, e139, e140, e141, e142, e143, e144, e145, e146, e147, e148, e149, e150, e151, e152, e153, e154, e155, e156, e157, e158, e159, e160, e161, e162, e163, e164, e165, e166, e167, e168, e169, e170, e171, e172, e173, e174, e175, e176, e177, e178, e179, e180, e181, e182, e183, e184, e185, e186, e187, e188, e189, e190, e191, e192, e193, e194, e195, e196, e197, e198, e199 ); TLargeEnumSet = Set of TLargeEnum; procedure TestLargeEnum; var LargeEnumSet: TLargeEnumSet; Enum: TLargeEnum; begin LargeEnumSet := [e011, e031, e051, e071, e091, e111, e131, e151, e171, e191]; Writeln('SizeOf = ', SizeOf(LargeEnumSet)); for Enum in LargeEnumSet do Write(Ord(Enum),' '); Writeln; end; begin try try TestLargeEnum; except on E: Exception do Writeln(E.ClassName, ': ', E.Message); end; finally Write('Press Enter: '); Readln; end; end. output on Win32 and Win64 What is the output on Linux?

Is there a QP report for this?

@Rollo62 That is indeed a safe way to do captures for anon methods.

https://my.embarcadero.com/#downloadsPage

I have no idea, Kas. I don't fiddle with the underlying Invision software.

That is a license breach.

He is on 10.3.3 Community edition.

Since I have a limited set of third party libs and plugins, my backup is to document the installation procedure. It doesn't take very long, IMO. The only thing that is somewhat annoying is the settings migration, but I have a registry file I keep handy to restore my preferred IDE settings.

@Anders Melander - I prefer the method that David describes. Return a documented error that can be handled. The criteria of the assert means you actually know the situation and should be able to do so. For me, asserts are contract validators that I use in debug mode. If the asserts hits me, I love to see it straight away in the debugger. I am not a fan of asserts in production code. Silly car analogy: Assert means you will drive off the road when you hit an unexpected turn. Asserts off and condition validation and error handling means you hit the brakes instead.

snake_kebab-case Oh, and the leet teenager edition sn4k3_k3b4b-c453

I often use code boxes and haven't had that happen to me. I'm using Chrome. Something I do see is that some old comment text I wrote earlier, sometimes shows up again in the reply editor.