Re: ping?
David Abrahams <[email protected]>
| Newsgroups | gmane.comp.lib.boost.langbinding |
|---|---|
| Message-ID | <[email protected]> |
Daniel Wallin <[email protected]> writes: > At 15:47 2003-09-12, David Abrahams wrote: > >>Hey Daniel, > > Hi. Sorry for my absence. > >>What's next? > > I don't know. The last thing I did was to implemented the recursive > overload resolution, but I recall there being some issues that I > didn't solve at the time. I'll look into this again. > > Have you looked at the code in the repository, A bit. > if so; please comment on it. OK: * Comments are needed describing how each thing fits into the big picture, and why. * Please try to use descriptive names for template parameters rather than simply "T" and "U". * default_converter_generator.hpp - U should be called "Direction" - Why do we have two directions selectably handled by the same class? I can't imagine where that would be important. You always know which direction you're going. - The implementation seems incomplete (where's the nested "type"?) - xxx_to_cpp and cpp_to_xxx are missing * empty.txt - What's this for? * extension_registry.hpp - What's this for? What's the template parameter? * Removing my copyright from slightly modified files isn't particularly cool * I think the plan is to refer to the license via "see accompanying LICENSE for conditions and terms of use." rather than embedding the license in the files directly. * I think the only way this is going to work out is for us to get boost/langbinding onto the main trunk and for me to start integrating it into Boost.Python forthwith. Alternatively, you could test your work by doing the Boost.Python integration. > Also Rene was going to put together some tests to confirm that the > shared library stuff works ok, I don't know how this is working > out. Rene? Also: I am starting to rethink the mechanism I'm using for wrapped function invocation, which among other things interacts with the nature and capabilities of call policies. I'm going to make a post about it; I hope you'll have input. The name "policies" is way too nebulous. I'm thinking we need at least two concepts: ConversionPolicies - a class affecting the precise method of converting arguments to or from XXX. CallPolicies - a refinement of ConversionPolicies which includes precall and postcall processing actions. Only applicable in the context of a wrapped function call. Thoughts? -- Dave Abrahams Boost Consulting www.boost-consulting.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf