factor/basis/xmode
Slava Pestov 602fe353e8 Fix another XMode bug 2009-03-28 22:19:55 -05:00
..
catalog Merge branch 'master' of git://factorcode.org/git/factor into regexp 2009-02-17 12:24:01 -06:00
code2html Fix another XMode bug 2009-03-28 22:19:55 -05:00
keyword-map Move web framework to basis 2008-09-04 18:15:13 -05:00
loader Changing : foo ; parsing to SYNTAX: foo ; 2009-03-21 01:27:50 -05:00
marker Fix another XMode bug 2009-03-28 22:19:55 -05:00
modes Move web framework to basis 2008-09-04 18:15:13 -05:00
rules Fixing xmode use lines; adding fake reluctant ?*+ to make XMode work (they're actually greedy) 2009-03-08 18:50:41 -05:00
tokens Get furnace and websites..concatenative to load 2008-12-17 19:39:02 -06:00
utilities Merge branch 'master' into regexp 2009-03-03 12:24:59 -06:00
README.txt Move web framework to basis 2008-09-04 18:15:13 -05:00
authors.txt Move web framework to basis 2008-09-04 18:15:13 -05:00
summary.txt Move web framework to basis 2008-09-04 18:15:13 -05:00
xmode.dtd Move web framework to basis 2008-09-04 18:15:13 -05:00

README.txt

This is a Factor port of the jEdit 4.3 syntax highlighting engine
(http://www.jedit.org).

jEdit 1.2, released in late 1998, was the first release to support
syntax highlighting. It featured a small number of hand-coded
"token markers" -- simple incremental parers -- all based on the
original JavaTokenMarker contributed by Tal Davidson.

Around the time of jEdit 1.5 in 1999, Mike Dillon began developing a
jEdit plugin named "XMode". This plugin implemented a generic,
rule-driven token marker which read mode descriptions from XML files.
XMode eventually matured to the point where it could replace the
formerly hand-coded token markers.

With the release of jEdit 2.4, I merged XMode into the core and
eliminated the old hand-coded token markers.

XMode suffers from a somewhat archaic design, and was written at a time
when Java VMs with JIT compilers were relatively uncommon, object
allocation was expensive, and heap space tight. As a result the parser
design is less general than it could be.

Furthermore, the parser has a few bugs which some mode files have come
to depend on:

- If a RULES tag does not define any keywords or rules, then its
  NO_WORD_SEP attribute is ignored.

  The Factor implementation duplicates this behavior.

- if a RULES tag does not have a NO_WORD_SEP attribute, then
  it inherits the value of the NO_WORD_SEP attribute from the previous
  RULES tag.

  The Factor implementation does not duplicate this behavior. If you
  find a mode file which depends on this flaw, please fix it and submit
  the changes to the jEdit project.

- References to non-existent rule sets in IMPORT tags and DELEGATE
  attributes were ignored in jEdit. They raise an error in Factor.

If you wish to contribute a new or improved mode file, please contact
the jEdit project. Updated mode files in jEdit will be periodically
imported into the Factor source tree.