On Fri, Jun 5, 2009 at 18:41, Oscar Nierstrasz<oscar@iam.unibe.ch> wrote:
But a more robust and forgiving parser is needed.
Well at least it would be nice if it could report errors, but that's a pain to do with LR parsers. I think I have an OMeta attempt somewhere but it will probably be slower than SmaCC. Personally I'd rather have a strict but simple parser and some assistance to fix bad .bib files than a permissive parser. Maybe one step would be to keep the current parser, but only use it to parse entries one by one instead of using a grammar rule for the whole file.
On Jun 5, 2009, at 16:20, Schwab,Wilhelm K wrote:
I found the problem: #newForWin32 is missing the #new, so it sends
That's a Rio bug then, please report it there.
the class to do an instance's job. Â I fixed that, but Monitcello was determined to undo my efforts. Â After a few tries at getting around that, I realized that it should run on Linux, so I did the installation there and then added my fix so that it should run on win32 also. Â That appears to have worked.
I find that it cannot parse my "real" .bib files, but it does seem to handle things that I build up from entries from Google scholar. The bib files in question are tested in the sense the LaTeX/BibTeX are happy with them, but I have yet to try bibclean on them. Â Is there any documentation or example code available?
Bill
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet