+1 a protected Context.createParser() would do the job.
Additionally I think that most (all?) method in Context should not be final: it is blocking extensions without any obvious need. Cheers, Marc. -- Web: http://www.efficient-webtesting.com Blog: http://mguillem.wordpress.com Kris Zyp wrote: > Would it be possible to make the Parser extensible? As far as I can > tell, I think it would basically involve change the Parser class's > methods to protected instead of private and create a property in the > Context that would allow for setting a custom Parser class rather than > hard-coding new Parser in compileImpl and stringIsCompilableUnit. This > would allow Rhino users to add syntactical extensions in the > environment, I believe. I would be glad to file a ticket/patch if that > is what it takes. > > Thanks, > Kris _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
