[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] C99 overriding GCC language
|
You can probably just change the schema of the extension point to be 0..*.
1..* is the default and I probably didn't change it.
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Mike Kucera
> Sent: Wednesday, May 16, 2007 11:04 AM
> To: CDT General developers list.
> Subject: [cdt-dev] C99 overriding GCC language
>
> Hi,
>
>
> I posted this comment to bug #186834
> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=186834).
> It hasn't gotten any feedback yet so I'm cross-posting it to the dev
> list...
>
> The problem is that the C99 language feature sometimes gets chosen as the
> default language for the C content type. This is not desirable as the
> brand
> new C99 parser is not yet as fast and robust as the DOM C parser.
>
> My proposed solution is to simply remove the content type mappings from
> the
> C99 language in the plugin.xml.
>
> The problem is that when I do this I get the following warning: "a minimum
> of 1
> 'contentType' elements must be specified".
>
> Does anyone know if there will be any adverse affects of having a language
> without having a content type mapped to it in the plugin.xml?
>
> One workaround would be to add a .c99 content type. But this seems
> unnecessary
> and adds clutter to the language mappings gui. Reusing existing content
> types
> is not a solution because that's what's causing this bug in the first
> place.
>
> Is there any reason not to change the schema for the language extension
> point
> to allow 0 contentType elements?
>
>
>
> Mike Kucera
> IBM CDT Team
> mkucera@xxxxxxxxxx
>
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
