but you should realize that like you cant necessarily assume that all of the pointers in the optree are valid post compilation.

The optree traversal code already exists in D::S, I'm not adding to or changing it, only trying to handle the exceptions that can arise from it.

be aware that data pointed to by the optree may not be allocated via SV allocation

I was aware the idea was a bit hookey and wouldn't handle some situations, only the preponderance of those I had encountered.

I also knew there is a better way, try{ } catch { }, but I couldn't get that to work. Turns out I was missing something simple and it is now working, so I can ditch the low-tide mark idea.

Now all I need is to figure out the gcc/posix equivalent of MSC __try{} __except()?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^2: [XS]:The address of the first dynamically allocated SV*? by BrowserUk
in thread [XS]:The address of the first dynamically allocated SV*? by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.