* Ara.T.Howard ([EMAIL PROTECTED]) [051213 12:45]: > now, why this seems to be platform dependant i do not understand yet - > but the combination of autoloading hooks, require overrides, and > non-protected (unless defined?...) class defs and method aliases seem > fragile.
The only thought I have at the moment is that if it's platform dependent, perhaps the require code in 1.8.4 is having difficulties with path separator variations among platforms. Perhaps there's some normalization going on but it's not 100%, meaning that "c:\foo\bar\baz.rb" is being stored (for require-once purposes) as "c:/foo/bar/baz.rb", but when the check is made against "c:\foo\bar\baz.rb" the normalizations isn't being done on the compare and "c:\foo\bar\baz.rb" != "c:/foo/bar/baz.rb" so the require is done a second time? Seems like something that would be caught very early though so I'm suspecting that ain't it. Rick -- http://www.rickbradley.com MUPRN: 946 | get the latest on random email haiku | all of our bargains, you need | to bookmark this page. _______________________________________________ Rails-core mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-core
