Mike Mattie wrote:
I am writing up that proposal, and a far more extensive patch. I do not mind the revert, I had asked for review in the RT.
To explain why I reverted, rather than let it go waiting for the full proposal: I'm not comfortable using an environment variable to alter the behavior of an opcode. Among other things, it's a global change, when you're more likely to want a very local selection of how you load libraries.
I really hope this does not sound whiny but review has been a problem for me. This is not the first revert for a lack of review. Could someone who is trusted please designate themselves as a reviewer for this particular issue ?
It's fair. This is a roadblock for someone who's doing good work on Parrot, so we want to get it cleared out as soon as possible. In this case, I'll do the review. For many patches a simple code review is enough, but this is a change that affects the core of Parrot deeply enough and broadly enough that it needs architectural review. I don't always see every message on the mailing list, but when I miss one, you can email me directly, email Coke or particle so they can remind me, or catch me on IRC during parrotsketch.
Allison
