Distinguish between tasserts that are caused by QI logic from those caused by an extension

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This came out of this PR thread. It would be nice if there was an easy way to distinguish between a tassert that is triggered in actual QI-owned extensions code, versus a tassert that is triggered because an extension did something wrong. For example, our host connector code may trigger a tassert if an extension has a null VTable entry, but that's an extension problem not a QI problem.

      Maybe this looks like adding a "component" to the assertion information? Or using a named error code for ExtensionError? 

            Assignee:
            Unassigned
            Reporter:
            Will Buerger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: