LYNX-DEV The method to tag soup madness

[Al Gilman]

  From: "Christopher R. Maden" <address@hidden>
  
  Hmm - did I say that?  Well, it depends on the class of error.
  Keeping a tree structure can help you realize when tags are
  mis-matched and tell you which ones probably need to be closed.  This
  will not match Netscape's behavior, which is to keep a couple of
  stacks; start-tags for elements of a class (like the font-changing
  class) will push formatting on the stack, and any end tag for that
  class will pop the stack.
  
So they are maintaining a pallette of classes and the language
tokens map to operations on the pallette.  Rather than a parse
stack, we have a [semilattice?] of states of the class pallette.
Operations on structure and finish classes are mostly disjoint.

I suspect that this is a more friendly paradigm for achieving the
Web Access Initiative objectives of graceful polymorphism that
parse trees.

--
Al Gilman  

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;