From: Trans Date: 2007-10-13T03:35:54+09:00 Subject: Re: ANN: English 0.1 On Oct 12, 10:32 am, Daniel Berger wrote: > On Oct 12, 11:06 am, "ara.t.howard" wrote: > > > > > On Oct 12, 2007, at 10:02 AM, Alex Young wrote: > > > > I hate to point this out, but isn't having "require 'english'" and > > > "require 'English'" both being valid and completely different going > > > to be rather confusing? > > > not only that but, on osx for one, case in-sensitive file names means > > that, regardless of whether you require 'english' or 'English', the > > first one of either type in your loadpath will be loaded: > > > cfp:~ > ruby -I . -r english -e 42 > > 42 > > > cfp:~ > ruby -I . -r English -e 42 > > 42 > > > so i think that users of osx will not even be able to load that via > > gems since the built-in English will be picked up first. > > Bad, bad, BAD!!! Well, it's no quite that bad. As I said there is no "require 'english'", so it should still work fine. > Keep the project name, but rename the library. Personally, I think a > toplevel namespace of "Language" is in order. Then end users could > "require 'language/english'". That's a reasonable idea ... though I have no plans to learn Japanese at this time ;) T.