[e-lang] What is defensive consistency?

[Dean Tribble]

I like the reliance set concepts because they really help clarify such
issues.  In this case, the answer is:

No, because if you already rely on the correctness of the other component,
and its contract includes some bound on operations, then you can just as
well rely on it for that too.

On 11/1/07, Raoul Duke <raould at gmail.com> wrote:
>
> hi,
>
> >
> http://waterken.sourceforge.net/javadoc/org/ref_send/promise/eventual/Eventual.html
>
> Clueless Newbie here.
>
> Does this line of thinking mean that to be super safe, no object would
> ever synchronously call any other? (You'd have to use futures or
> something (Eventuals) - couldn't even use e.g. Erlang style message
> passing because your plan could get pre-empted by the scheduler to
> handle one of the messages you generated, in another process.)
>
> You could call your own instance methods (and hope your code doesn't
> have bugs wrt internal plans) but nobody else's? I'm just thinking it
> could be hard to know what calls on other instances could screw up
> your own plans.
>
> sincerely.
> _______________________________________________
> e-lang mailing list
> e-lang at mail.eros-os.org
> http://www.eros-os.org/mailman/listinfo/e-lang
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.eros-os.org/pipermail/e-lang/attachments/20071101/07626617/attachment.html