Re: Re: Inheritance graph

At 10:01 2003-08-14, David Abrahams wrote:
>Daniel Wallin <[email protected]> writes:
>
> > Forgot this in my first response..
> >
> > At 01:37 2003-08-14, David Abrahams wrote:
> >>Daniel Wallin <[email protected]> writes:
> >>
> >> > FYI, I've messed around with the code in inheritance.cpp /
> >> > inheritance.hpp and made it into a real singleton. In this process I
> >> > also investigated type importing, and to me it seems complicated to
> >> > try to share any data at all between modules.
> >>
> >>Yes, it's at least complicated.  However, given the size of the cache
> >>it does seem expensive not to share when multiple modules interact.
> >
> > Perhaps we could restrict importing so that you can only import entire
> > modules?
>
>I don't think I intended otherwise.
>
> > In that case all interacting modules could share both cast-graph and
> > cache. What do you think?
>
>I think it sounds lovely.
>
>     import foo("my.package.foo");
>
>     ...
>
>     foo.attr("f")(1, 2); // call a function in foo
>
>     // as above, but imports all conversions and cast graph.
>     import_extension bar("my.package.bar");
>
>     ...
>
>     bar.attr("x") = 3;
>
>??

Looks great for the python layer at least. In luabind we would only import the
converters and the cast graph, since we can't load external modules.

---
Daniel Wallin



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01