On Tue, 13 Dec 2005, Jeremy Kemper wrote:

> Hi all.
>
> Rails segregates 'framework' and 'app' files so the latter may be reloaded
> per-request during development.  The result is a quick, responsive dev
> environment, but it means Rails is going out of its way to implement a
> feature that Ruby does not natively provide.
>
> We can't tell whether two different paths refer to the same file so you'll
> see double-requires depending on your load path.

   why not?  a combination of expand_path, mtime, and an md5 of some/all of the
   file would work on any platform.

> You shouldn't see them in the framework itself since it uses 'normal'
> requires.  Otherwise we'd hit an inf. loop wrapping already-wrapped methods
> (as Ara reports.)

   i am, in fact, seeing it in the framework.

> Unfortunately, I am unable to reproduce on 1.8.3 or .4p2 with Rails 1.0rc5
> running Linux or MacOS X.  I will try 1.8.2 + FreeBSD shortly.
>
> Please note: there is a rails-core list for which this thread is well
> suited.  (I hope this error is not an issue with Ruby itself.)
>
>  http://lists.rubyonrails.org/mailman/listinfo/rails-core

   thanks for the info.  i'll move the thread there with a link to this thread
   - anyone know how to provide a http link for this thread?  (who archives it
     online?)

regards.

-a
-- 
===============================================================================
| ara [dot] t [dot] howard [at] noaa [dot] gov
| all happiness comes from the desire for others to be happy.  all misery
| comes from the desire for oneself to be happy.
| -- bodhicaryavatara
===============================================================================