On Tue, Dec 23, 2008 at 3:51 PM, Christian Neukirchen
<chneukirchen / gmail.com> wrote:
> Dave Thomas <dave / pragprog.com> writes:
>> On Dec 22, 2008, at 1:44 PM, Charles Oliver Nutter wrote:
>>> It probably could use the same lock; the trickier bit is that in
>>> between encountering the autoload and requiring the file there's
>>> already state changes happening. So I think we still need to ensure
>>> the autoload marker is mutated under lock as well.
>>>
>>> To be honest, I'm not sure autoload is really even possible to make
>>> safe in the presence of threads...the design of it may be inherently
>>> incompatible. But I'm willing to talk through some possibilities and
>>> see what we can come up with.
>>
>> Yeah--you'd need to make require transactional somehow.
>>
>> Stupid question: does anyone actually use autoload?
>
> Rack does.  Merb does as well.

So does RbGCCXML, a random library that I'm using (I see no point as
to why it's doing so, to be honest).

-austin
-- 
Austin Ziegler * halostatue / gmail.com * http://www.halostatue.ca/
               * austin / halostatue.ca * http://www.halostatue.ca/feed/
               * austin / zieglers.ca