Greg Stein wrote:
...
> Being able to place them into function attributes means that you have a
> better *model* for how you record these values. Why place them into a
> separate mapping if your intent is to enhance the semantics of a function?
> If the semantics apply to a function, then bind it right there.
BTW., is then there also a way for the function *itself*
so look into its attributes? If it should be able to take
special care about its attributes, it would be not nice
if it had to know its own name for that?
Some self-like surrogate?
ciao - chris
--
Christian Tismer :^) <mailto:tismer@appliedbiometrics.com>
Applied Biometrics GmbH : Have a break! Take a ride on Python's
Kaunstr. 26 : *Starship* http://starship.python.net
14163 Berlin : PGP key -> http://wwwkeys.pgp.net
PGP Fingerprint E182 71C7 1A9D 66E9 9D15 D3CC D4D7 93E2 1FAE F6DF
where do you want to jump today? http://www.stackless.com
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