comment on

<plug>Perhaps Closure on Closures (beta) would be of help in shedding closures of their enigma.</plug>.

Broquaint please do not feel that you need to add <plug> tags to comments like this. The node you wrote is well written, informative and useful. You have every right to feel proud about the node and to refer people to it when necessary. My only beef with the node is that due to implementation problems I feel the term closure has special meaning in Perl and should be restricted to only a class of anonymous subs, however I am aware that I am most likely in the minority with this opinion.

DigitalKitty should certainly review your node, and if you hadn't provided a link I would have done so myself.

:-)

---
demerphq

_{<Elian> And I do take a kind of perverse pleasure in having an OO assembly language...}

In reply to Re: Re: Help with the concept of closures. by demerphq
in thread Help with the concept of closures. by DigitalKitty

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.


Just another Perl shrine
	PerlMonks