comment on

> I don't really see a win with this style, though, over giving test a parameter, and just using standard function calls (I had a little play with coroutines on the way but that's really overkill for this).

Well I expected decorators to be more flexible, i.e. to redefine test() by putting a wrapper around it and not to built a new decorator @test (!?!)

But I'm not too proficient with Python, and I'm misunderstanding the code.

(well, there must be a reason why I prefer Perl's syntactic flexibility. ;-)

I suppose def _(a) is a way to workaround the limitations of lamda?

Is the name _ special (magic) or is it just a convention?

Cheers Rolf

( addicted to the Perl Programming Language)

In reply to Re^6: RFC: Simulating Ruby's "yield" and "blocks" in Perl (Python) by LanX
in thread RFC: Simulating Ruby's "yield" and "blocks" in Perl by LanX

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.


There's more than one way to do things
	PerlMonks