> Why not have the block automatically be inserted into acquire's argument
> list? It would probably get annoying to have to define inner functions
> like that every time one simply wants to use arguments.
But the number of *uses* would be much larger than the number of
"block decorators" you'd be coding. If you find yourself writing new
block decorators all the time that's probably a sign you're too much
in love with the feature. :-)
> For example:
>
> def acquire(block, aLock):
> aLock.acquire()
> try:
> block()
> finally:
> aLock.release()
>
> @acquire(myLock):
> code
> code
> code
>
> Of course, augmenting the argument list in that way would be different
> than the behavior of decorators as they are now.
I don't like implicit modifications of argument lists other than by
method calls. It's okay for method calls because in the x.foo(a) <==>
foo(x, a) equivalence, x is really close to the beginning of the
argument list.
And your proposal would preclude parameterless block decorators (or
turn them into an ugly special case), which I think might be quite
useful:
@forever:
infinite loop body
@ignore:
not executed at all
@require:
assertions go here
and so on.
(In essence, we're inventing the opposite of "barewords" in Perl here, right?)
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
