Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[Dltk-dev] Re: multiple source parsers


 almost forgot, there is now an AbstractSourceParser base class that all ISourceParser implementations should inherit from that takes care of the 'informational' method implementations.

On Nov 30, 2007 4:01 PM, Jae Gangemi <jgangemi@xxxxxxxxx> wrote:
hello all -

  i've just committed the initial changes required to start allowing multiple source parser extension point implementations (a unit test too!). aside from a package change for ISourceParser and the schema changes, all other underlying functionality remains the same.

  if anyone out there is working against the HEAD in cvs, you will need to update your sourceParser extension point to look something like this:

   <extension point="org.eclipse.dltk.core.sourceParsers ">
      <parserContribution natureId="org.eclipse.dltk.tcl.core.nature">
         <parser
               class="org.eclipse.dltk.tcl.internal.parser.TclSourceParser"
               description="Tcl Source Parser"
               id="org.eclipse.dltk.tcl.sourceParser"
               name="Tcl Source Parser"
               priority="0" />
      </parserContribution>
   </extension>

  the next steps will be to build a preference page that allows you to choose the parser, and then to update calls that retrieve the parser to determine which one to use based upon the user's preferences. once that's done, my plan is to allow for project specific parsers and use that as a basis to start adding some other project specific options (specifically selecting which interpreter to use and allowing for project specific debugging preferences [ie: break on first line, etc]).

--
-jae



--
-jae

Back to the top