That would be fine, but we'd also need to go through the Rails framework and replace all the foreach calls with our new custom method. And train people to use it in the future instead of the stock foreach.
On Sep 13, 2006, at 3:36 PM, Andrew Kaspick wrote: > > Why not wrap Dir.foreach in a custom method or something and do the > ordering in that? ie. get all the files, sort the array, return it. > > On 9/13/06, Nex3 <[EMAIL PROTECTED]> wrote: >> >> Solomon White wrote: >>> Makes sense -- we've run into issues before where load order varied >>> between platforms and caused inconsistent behavior. I wonder if we >>> should monkeypatch Dir.foreach to be sorted and fix this at a higher >>> level? There are probably other places in the framework where >>> inconsistent load order could (does?) induce weirdness. Off the >>> top of >>> my head, I can't think of any bad side effects of forcing consistent >>> ordering across the board for Dir.foreach... Thoughts? >>> >> >> I think that if there is a program somewhere that relied on >> Dir.foreach >> having a particular order, it would break anyway if moved across >> platforms, so breaking it by doing this will just make it break >> faster. >> >>> >> > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core -~----------~----~----~----~------~----~------~--~---
