[Interest] Disavowing the Lakos Rule for Q_ASSERT

[Turtle Creek Software]

I added a deliberate exception throw in our GUI code, reporting a button we
forgot to add to a layout.  It's typical of our sanity-checking.

Attached is the stack trace from there to the event loop. It's in QT 5.15
running on Mac Mojave Intel, the latest that can still catch and continue.
A screen shot since text wasn't selectable in Qt Creator.

All the code appears to be event-handling and event loop in Qt and Cocoa.
Those are the places we'd like to still pass along exceptions in ARM.

Managing exceptions in the whole body of Qt code sounds like a huge
project.  But practically speaking, user error handling may never pass
through the places that are hard to change.

Maybe it's worth discussing with users, to see how they actually use
exceptions?  Focusing on those places would be good enough.

Right now we build for Intel to test against the old app easily.  Next time
back on ARM I'll try to get a stack trace there.  For Intel, no Apple code
seems to be along the path from error check to notify().

Best, Casey McDermott
TurtleSoft.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20240905/7cb45a3a/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Throw-Stack-Trace.png
Type: image/png
Size: 215472 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20240905/7cb45a3a/attachment-0001.png>