| RE: [cdt-dev] Loose end # 2 - contenttype extensionsandcasesensitivity |
In case anyone else on the list is interested in following the progress:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=105022
Jeremiah
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mike Wilson
Sent: Sunday, July 24, 2005 11:33 AM
To: CDT General developers list.
Subject: RE: [cdt-dev] Loose end # 2 - contenttype extensionsandcasesensitivity
This behavior doesn't seem completely reasonable to me. Why don't you enter a bug against the platform core component and put me on the CC list. I'll discuss it with the person who did the content type support.
McQ.
"Lott, Jeremiah" <jeremiah.lott@xxxxxxxxxxx>
Sent by: cdt-dev-bounces@xxxxxxxxxxx07/22/05 14:55
"CDT General developers list."
"CDT General developers list." <cdt-dev@xxxxxxxxxxx> RE: [cdt-dev] Loose end # 2 - content type extensionsandcasesensitivity
It's not JDT behavior, it is core platform behavior. I agree 100%, but you can't even specify .c and .C as separate extensions. The content type system automatically converts any extension to lowercase before doing a compare. All extension methods return lowercase, regardless of what you specify in plugin.xml or in the UI. I actually modified CDT to include a content type mapping for ".S", but it made no difference as the platform converted it to lowercase after reading it.
Jeremiah
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Recoskie, Chris
Sent: Friday, July 22, 2005 2:55 PM
To: CDT General developers list.
Subject: RE: [cdt-dev] Loose end # 2 - content type extensionsandcasesensitivity
I don’t think we can follow that per se though as we have to build .c files as C and .C files as C++
Do we really know if this is defined Eclipse behaviour or is it just the way that JDT has implemented it?
If the API spec doesn’t specify one way or the other then I’d say we’re free to handle it whichever way we wish, i.e. in a case sensitive manner.
___________________________________________
Chris Recoskie
Software Designer
IDE Frameworks Group
Texas Instruments, Toronto
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Lott, Jeremiah
Sent: Friday, July 22, 2005 2:32 PM
To: CDT General developers list.
Subject: RE: [cdt-dev] Loose end # 2 - content type extensions andcasesensitivity
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