On Mon, 04 Oct 2010, Joe Blaylock wrote: > On Sat, 2010-10-02 at 17:06 -0700, Invenio Trac wrote: >> (WRT `foo-bar` it may not be connected to `U(1)` indeed, I only wanted to >> point out the similarity in the sense that if there is no blank space >> before dash (or inside parens), then dash/parens should not be interpreted >> as special chars by the parser, but treated as regular alphanumeric chars >> only.) > > Yes, of course you're right. Indeed, this is the way I interpreted it > when I read it, and it was just the hint I needed to make finding and > fixing the problem super-fast. So thanks. :)
Could this kind of fix be applied to the `(U(1) OR SL(2,Z))' failed regression test case as well, to kill the two tasks in one go? Kind of like if you see `(...)' where `...' does not contain spaces, replace it by `__OPENPAREN__...__CLOSEPAREN__' before proceeding to the regular paren parsing, then parse into units as usual, then replace underscore variables back. Kind of what I had done in the past to temporary replace spaces by __SPACE__ in the main parser in order to work around quoted expressions, see `grep __SPACE__ search_engine.py'. It would be nice to fix this failed regression test case too, and it looks so similar to the hep-th case :) but I had not looked at the problem if it is indeed that. Best regards -- Tibor Simko
