"Phillip J. Eby" <pje at telecommunity.com> writes: > Indeed, even pystone doesn't do much attribute access on the first argument > of most of its functions, especially not those in inner loops. Only > Proc1() and the Record.copy() method do anything that would be helped by > SELF_ATTR. But it seems to me that this is very unusual for > object-oriented code, and that more common uses of Python should be helped > a lot more by this. Is it that unusual though? I don't think it's that unreasonable to suppose that 'typical smalltalk code' sends messages to self a good deal more often than 'typical python code'. I'm not saying that this *is* the case, but my intuition is that it might be (not all Python code is that object oriented, after all). Cheers, mwh -- The source passes lint without any complaint (if invoked with >/dev/null). -- Daniel Fischer, http://www.ioccc.org/1998/df.hint
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