From: Luke Graham <spoooq@...>
Date: 2005-04-05T13:37:35+09:00
Subject: Re: Ruby rite (Ruby 2.0) vaporware or real?

On Apr 5, 2005 7:59 AM, gabriele renzi <surrender_it@remove-yahoo.it> wrote:
> Luke Graham ha scritto:
> > On Apr 4, 2005 3:10 PM, Luke Graham <spoooq@gmail.com> wrote:
> >
> >
> >>Interface inheritance can be done by just including the base module
> >>and any extra child modules in the list to be checked.
> >
> >
> > I guess this list could be in the child interface or somewhere else.
> >
> 
> take a look at the various Interface libraries on RAA
> (raa.ruby-lang.org). They check somewhat at "compile time".
> 
> 

I took a quick look at ruby-contract's API, and it seems quite comprehensive.
Maybe one day I'll meet a problem that needs this solution, so its good to
know whats out there.

I had a toy distributed app once to investigate the ideas of changing
behaviour at run-time, and some different architectures suggested themselves.
One was to allow multiple copies of the basic app, which people could write
objects in (the heart of the app was really just an interpreter), and then those
objects could be shared with others, either being called directly or
having copies
sent. Error-checking always seemed like it would be one of the biggest problems
and this sort of thing would address at least one aspect of that.

OT: I always wanted the ability to reverse out changes to objects, such as
unmixing modules. That would be the missing piece of the puzzle as
far as my app went.

-- 
spooq