
Hello, the langbinding list is abandoned, the cvs directories empty, nothing seems to be in the vault and i started the same thing (a generic langbinding library). So please tell me, is langbinding still developed or should i continue mine? PS: i had that aha moment when i realised that dispatch on all arguments can also be used for multiple dispatch within C++. That would be a nice boost library: a generic dispatcher for foreign languages and C++ itself. Right now i am finding out whether one can write an awkward-syntax-predicate- dispatcher in c++. what is the world's opinion on all this, i would like to know.

On 12/16/06, Sascha Krissler <boost-dev@k.datenfreihafen.de> wrote:
the langbinding list is abandoned, the cvs directories empty, nothing seems to be in the vault and i started the same thing (a generic langbinding library). So please tell me, is langbinding still developed or should i continue mine?
Dave A. can probably give a more to-the-point answer, but I think the language-agnostic Boost.Langbinding library is a project in search of a sponsor. If someone can pay for the Boost Consulting resources to work on it, it will get done. I think it looks like the greatest thing since sliced bread, but I don't have enough political capital to get the funding from my current employer. Here's hoping someone else *does*. -- Caleb Epstein

Sascha Krissler <boost-dev@k.datenfreihafen.de> writes:
Hello,
the langbinding list is abandoned, the cvs directories empty,
Not on the "langbinding" branch they're not.
nothing seems to be in the vault and i started the same thing (a generic langbinding library). So please tell me, is langbinding still developed or should i continue mine?
It's definitely in stasis.
PS: i had that aha moment when i realised that dispatch on all arguments can also be used for multiple dispatch within C++. That would be a nice boost library: a generic dispatcher for foreign languages and C++ itself. Right now i am finding out whether one can write an awkward-syntax-predicate- dispatcher in c++.
Huh? What's that? -- Dave Abrahams Boost Consulting www.boost-consulting.com

On Mon, Dec 18, 2006 at 04:45:18PM -0500, David Abrahams wrote:
boost library: a generic dispatcher for foreign languages and C++ itself. Right now i am finding out whether one can write an awkward-syntax-predicate- dispatcher in c++.
Huh? What's that?
in the same sense not perfect like boost::lambda is not becuase of the syntactic restrictions of c++. so somewhere in the middle between unusable and without syntactic clutter

Sascha Krissler <boost-dev@k.datenfreihafen.de> writes:
On Mon, Dec 18, 2006 at 04:45:18PM -0500, David Abrahams wrote:
boost library: a generic dispatcher for foreign languages and C++ itself. Right now i am finding out whether one can write an awkward-syntax-predicate- dispatcher in c++.
Huh? What's that?
in the same sense not perfect like boost::lambda is not becuase of the syntactic restrictions of c++. so somewhere in the middle between unusable and without syntactic clutter
I think I'm wondering less about the awkward-syntax than about the "predicate-dispatcher" part. -- Dave Abrahams Boost Consulting www.boost-consulting.com

On Tue, Dec 19, 2006 at 03:04:38PM -0500, David Abrahams wrote:
Sascha Krissler <boost-dev@k.datenfreihafen.de> writes:
On Mon, Dec 18, 2006 at 04:45:18PM -0500, David Abrahams wrote:
boost library: a generic dispatcher for foreign languages and C++ itself. Right now i am finding out whether one can write an awkward-syntax-predicate- dispatcher in c++.
Huh? What's that?
in the same sense not perfect like boost::lambda is not becuase of the syntactic restrictions of c++. so somewhere in the middle between unusable and without syntactic clutter
I think I'm wondering less about the awkward-syntax than about the "predicate-dispatcher" part.
when you regsiter a candidate method to the multimethod you can optionally pass a function returning bool and the candidate method is only called when the function returns true. This is a generalization of normal multiple dispatch and emulates the latter with: bool fun(argn, ...) { return dynamic_cast<T1>(arg1) && dynamic_cast<T2>(arg2); } the nontrivial part is the ordering of the predicates so that arg1->property1() && arg2->property2() is tested before arg1->property1() because the former is more specific. i was thinking about passing the predicate as a lambda expression and then work on it with a compile time algorithm that operates on the parse tree of the expression template.

On a related note, pyd, python bindings for 'D', was just released. It claims to be based on boost::python design.
participants (4)
-
Caleb Epstein
-
David Abrahams
-
Neal Becker
-
Sascha Krissler