Description: ------------ The file-parsing code does not handle strings properly, and gets confused when @ signs appear in strings (as in \latex@macro). The test below is distilled from my preamble. Frankly, parse() and parseEntry() are a terrible mess and should be refactored into a state machine that distinguishes top-level, in-entry and in-string states. The first embedded @ in the test triggers a warning TWICE, then the second gets stuck in the loop... Test script: --------------- cat > example.php @PREAMBLE{ "{@url} @..." } ^D Expected result: ---------------- The code should terminate Actual result: -------------- infinite loop

I can confirm the bug in handling the '@' sign in entries. I came across the problem, when I had an entry that contained a '@' in an entry. The result was a crash when the memory of PHP was exhausted. My workaround was to comment out the lines in the beginning of the "parser" function that starts with if ((0 != $open) && ('@' == $char)) Otherwise, I agree with alexis, that the code is hard to read. Instead of transforming the code to a state machine, it might be more rewarding to directly use a parser generator (like http://pear.php.net/package/PHP_ParserGenerator) to generate the parser. Best regards Olaf