David Abrahams <dave@boost-consulting.com> writes: > My users want extension modules to be able to control how their > attributes are imported when using "import *". In particular, > Boost.Python includes a kind of multimethod facility, and some of my > users would like it if > > from bpl_extension import * > > caused multimethod definitions in bpl_extension to be /merged/ into > the current module, rather than replacing any multimethod bindings > with the same name in the current module. Eww. I can see where the idea is coming from, but allowing arbitrary magic somewhere only name binding is allowed today sounds horrible to me. Cheers, M. -- please realize that the Common Lisp community is more than 40 years old. collectively, the community has already been where every clueless newbie will be going for the next three years. so relax, please. -- Erik Naggum, comp.lang.lisp
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