> From: Skip Montanaro
>
> Yes. I was thinking of the case where we wanted it to return
> something
> useful which could be bound to the name "foo". I suppose if
> you've had too
> much caffeine you could dream up a case where w1() returns an
> AST based on
> the original foo and w2() does something with it to cook up a
> new object,
> but I suspect that would be pretty rare.
You could create some lovely obfuscated code ...
def decorator (func):
return 1
def func [decorator] (a, b):
return 2
print func(3, 4)
...
TypeError
:)
BTW, I have to say that looking at it, I don't like the decorator before the arguments. I'm immediately trying to read it as:
func (decorator) ...
It's something I think I could eventually get used to, but I don't find it very readable. I guess there's not enough languages that do something like that.
Tim Delaney
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4