Lars Fosdal

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.

AFAIK, editing posts and comments doesn't trigger a notifications for others - so if the intent is to make the update visible, adding a new comment is probably the best approach. Those that have been active in the thread will then get notified.

I agree - unless we are talking about old-ish replies? Personally, I am ok with a freeze after so many (days?) policy. Any correction after than can be done in a new comment? Edit: There have been episodes where members have modified their posts/comments a long time after they were written. Usually in the context of "leaving in anger".

Is there actually a freeze after a certain period?

I know @Daniel tweaked something - but it was supposed to only affect the EMBT people's inability to edit their own posts?

Anders, With Assert If In_The_Shit then Panic Without Assert If In_The_Shit then DoOurBestToCope else BizAsUsual;

David, The full callstack at the time of the assert is in the first attached QPInfo file of https://quality.embarcadero.com/browse/RSP-31944 Added the extract in a comment.

Please give your post a meaningful title.

Just want to add that I loved the way it worked up until that error which hopefully can be quickly remedied.

@David Millington Unable to reproduce in small example. But, uninstalled the Parallel Debugger - and the Assert fail no longer happened. Created a QP https://quality.embarcadero.com/browse/RSP-31944

Repeatable. And - it brings down the IDE. Will be checking if it is possible to make a small example when I get time.

I had a failing assert in some CPP code - which I sort of assume is this plugin, since I've never seen it before. It happened on a breakpoint in an exception handler, and it brought down the IDE. Asserts in production code is not a good practice.

There is a fallback to the free version for GitKraken as far as I can tell?