Re: [cdt-patch] New Parser in HEAD branch

[David Inglis <dinglis@xxxxxxx>]

Since 2.0 there is a getPluginPreferences on Plugin. so I'm not sure
why that would not build for you.

See http://dev.eclipse.org:8080/help/content/help:/org.eclipse.platform.doc.isv/reference/api/org/eclipse/core/runtime/Plugin.html#getPluginPreferences()

Schaefer, Doug wrote:
> Like I wouldn't have tried that ;-).
>
> Unfortunately, you can only have preference store on UI plugins (not sure
> why).  The code you suggest fails to compile.
>
> Cheers,
> Doug Schaefer
> Senior Staff Software Engineer
> Rational Software - IBM Software Group
> Ottawa (Kanata), Ontario, Canada
>  
>
> -----Original Message-----
> From: Alain Magloire [mailto:alain@xxxxxxx] 
> Sent: Thursday, March 06, 2003 9:48 AM
> To: cdt-patch@xxxxxxxxxxx
> Subject: Re: [cdt-patch] New Parser in HEAD branch
>
>
> > This is a pretty big patch, but it is the merge of the NewParser1 branch
> > into the HEAD branch.  We will do futher work on the parser and everything
> > associated with it in the HEAD branch.  Highlights of the patch include:
> >
> >
> >
> > *	Parser in the "parser" source folder in cdt.core
> > *	Preference in the C/C++ preference page to enable/disable use of the
> > new parser (disabled by default)
>
>
> Suggestion:
> You could probably use the Core plugin preferences instead which will make
> more
> sense then setting this on the UI plugin, and there will be no hack like
> this.
>
>  +               
>  +               // TODO - temporary kludge (maybe) to make sure the core
> preferences
>  +               // are kept in sync with the stored preferences
>  +
> CCorePlugin.getDefault().setUseNewParser(CPluginPreferencePage.useNewParser(
> ));
>  
>
> And then do the check correctly in the parser:
>
>  
> CCorePlugin.getDefault().getPluginPreferences().getDefaultString(PREF_USE_NE
> W_PARSER);
>
> Since the preference affect a Core setting doing this on the Core plugin
> will simplify things,
> i.e. no need to sync.
>
> _______________________________________________
> cdt-patch mailing list
> cdt-patch@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-patch
> _______________________________________________
> cdt-patch mailing list
> cdt-patch@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-patch