Re: [cdt-dev] Loose end # 2 - content type extensions and casesensitivit

[Doug Schaefer <dschaefer@xxxxxxxxxx>]

I've seen too many uses of .C for C++ files to be comfortable with this. 
We need to match what the file system will do. Is there a bug on the 
platform guys for this?


Lott, Jeremiah wrote:

> My investigation lead me to believe that Eclipse treats all file 
> extensions in content types as case insensitive on all platforms (I 
> tried windows and linux).  This was independent of CDT.  I tried JDT, 
> adding extensions like ".JAVA", and also by inspecting the 
> Eclipse content type code.  I would actually prefer they be 
> case-sensitive, but given this Eclipse behavior, I don't see any 
> choice but to follow the requirements set by the Eclipse platform and 
> treat them as case-insensitive.
>  
>   Jeremiah
>
>     -----Original Message-----
>     *From:* cdt-dev-bounces@xxxxxxxxxxx
>     [mailto:cdt-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Treggiari, Leo
>     *Sent:* Friday, July 22, 2005 2:35 PM
>     *To:* CDT General developers list.
>     *Subject:* [cdt-dev] Loose end # 2 - content type extensions and
>     casesensitivity
>
>     In bug 103530, there is a discussion of whether the file
>     extensions specified for an Eclipse content-type should be treated
>     as case sensitive or case insensitive.  Currently, the MBS treats
>     these as case sensitive on all platforms.  In there is a consensus
>     on what is correct, and it is different from the current MBS
>     behavior, we could try to change this for 3.0.  What do others think?
>
>      
>
>     Thanks,
>
>     Leo
>
>      
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>  


--
Doug Schaefer, Senior Software Developer
IBM Rational Software, Ottawa Lab
Kanata, Ontario, Canada