http://d.puremagic.com/issues/show_bug.cgi?id=7730


Don <clugd...@yahoo.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |clugd...@yahoo.com.au


--- Comment #10 from Don <clugd...@yahoo.com.au> 2012-03-21 02:21:57 PDT ---
(In reply to comment #5)
> The problem at the moment is that the capitalisation of a module's name, in 
> the
> absence of a module declaration, depends on the name by which it is 
> referenced.
>  Try this at home:
> 
> ----- modulecap_a.d -----
> import modulecap_b;
> ----- ModuleCap_b.d -----
> int x = .y;
> ----------
> C:\Users\Stewart\Documents\Programming\D\Tests>dmd modulecap_b.d
> modulecap_b.d(1): Error: undefined identifier module modulecap_b.y
> 
> C:\Users\Stewart\Documents\Programming\D\Tests>dmd ModuleCap_b.d
> ModuleCap_b.d(1): Error: undefined identifier module ModuleCap_b.y
> 
> C:\Users\Stewart\Documents\Programming\D\Tests>dmd modulecap_a.d
> modulecap_b.d(1): Error: undefined identifier module modulecap_b.y
> ----------
> 
> I can imagine this leading to havoc if the same module is referenced from
> different modules by different capitalisations of the name.
> 
> If there's a module declaration, go with that.  Otherwise, go with the actual
> capitalisation of the filename, thereby ensuring platform-consistent 
> behaviour.
> 
> That said, are there any 32+-bit platforms on which filenames aren't
> case-retentive?

Not according to this:
http://en.wikipedia.org/wiki/Filename

Moreover, it seems that anything which doesn't retain case, doesn't allow very
long filenames. I can't see any reason to require lowercase. It is simple to
require that filename case matches module case.

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------

Reply via email to