[j-devel] PHP mode fixes and improvements

[Peter G. <pe...@ar...>]

This morning's 0.15.3+ development snapshot is up:

    http://armedbear.org/j.zip          (source)
    http://armedbear.org/j-jar.zip      (just j.jar)

In prior versions, j was re-using a bunch of Java mode code for PHP
mode, and as a result, didn't handle multi-line quoted strings
correctly in PHP mode. This problem affected findMatchingChar, and it
became a lot more conspicuous when you set highlightBrackets = true.

Starting with this snapshot, PHP mode has its own syntax iterator,
which should handle multi-line quoted strings much better. Samo's
example now works correctly, at least as far as bracket highlighting
is concerned. I haven't looked at indentation specifically, although
it should benefit from the new syntax iterator too. Please let me know
what I'm missing; I don't actually write PHP code myself, so I don't
get any incidental opportunities to test PHP mode.

J now recognizes automatically that files that start with "<?php"
should be opened in PHP mode, regardless of their filename.

In Lisp and Scheme modes, there was a very weird formatting problem if
j encountered '#' not followed or preceded by '|' ("#|" being Lisp's
answer to "/*"). This bug is now fixed.

If you add a line to ~/.j/prefs to use custom keywords for a
particular mode, it is now no longer necessary to restart j to pick up
the new keywords. J does not, however, automatically detect the change
if you modify the keywords file itself; until I get around to
implementing a fileSaved event, the workaround is to make some
meaningless change to ~/.j/prefs (e.g. space, backspace) and save it,
which forces j to reset the keywords in all the active modes.

Thanks for your support.

-Peter