I don't know about anyone else, but I am stopping here. Problem 1 I know can be done, I have seen the solution, but I remember at the time thinking that I didn't care to know typeglobs well enough to figure that out. Problem 3b I ran afoul of Perl's "return by value" semantics, and I don't know any tricks offhand for that.

Problem 9 I might be able to do, but I won't. I am guessing is done by something like finding internal variables used for caller, causing the variables to change from eval to eval and between being in an eval and not being in an eval. I don't have enough interest to look up the implementation to find that. (If that approach even works.)

The bonus question looks like something where I either would need to know the internals better or monitor p5p. Since I do neither, I don't know that.

Let this be a lesson for those who mistakenly thought that I was some form of a perl deity. As I have said all along, I am far from it. Go bug TimToady, TheDamian, chip, etc if you want to see true Perl mastery.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.