From: Lloyd Zusman <ljz@...>
Date: 2005-09-11T11:58:56+09:00
Subject: Re: Problem fixed, but why? (was: Rio 0.3.4)

"rio4ruby" <rio4ruby@rubyforge.org> writes:

> Lloyd Zusman wrote:
>> Wybo Dekker <wybo@servalys.nl> writes:
>> I found a work-around for this problem, but I don't understand why it
>> fixes it, and why the module wasn't functioning properly in the first
>> place.
>>
> I still can't reproduce this. The Rio software is broken up over many
> (perhaps too many) files, and somehow you got to code that was
> including that module before it was evalutated by the interpreter. I
> think your patch is right on target. That code really should be right
> where you put it. I have made that change permanent -- it will be in
> the next release. Thanks!
>
> Cheers,
> -Christopher

I'm glad to help :)

I'm wondering if this behavior has something to do with the way that the
gem system evaluates files that it includes.  This might have some
subtle idiosyncracies.

But anyway, it works now, and that's what's most important.  All's well
that ends well!

Thanks.


-- 
 Lloyd Zusman
 ljz@asfast.com
 God bless you.