in reply to [XS]:The address of the first dynamically allocated SV*?

I think you should ask on P5P, but you should realize that like you cant necessarily assume that all of the pointers in the optree are valid post compilation. One of the processes in the compilation phase may leave these pointers undefined, for instance if they have been optimised away.

Also, be aware that data pointed to by the optree may not be allocated via SV allocation, as the memory will be shared memory and not process specific memory.

demerphq

  • Comment on Re: [XS]:The address of the first dynamically allocated SV*?

Replies are listed 'Best First'.
Re^2: [XS]:The address of the first dynamically allocated SV*?
by BrowserUk (Patriarch) on Oct 05, 2008 at 23:41 UTC
    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.
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom