Re: Parser.XML.Tree

2007-03-19 Thread Martin Bähr
On Mon, Mar 19, 2007 at 09:15:00AM +, Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum wrote: > Mainly because having one class per node type is a more object- > oriented approach, how does having more classes make something more object oriented? what a class or an object is should r

Parser.XML.Tree

2007-03-19 Thread Henrik Grubbstr�m (Lysator) @ Pike (-) developers forum
Mainly because having one class per node type is a more object- oriented approach, and it also leads to much improved type-checking and optimizer possibilities.

Parser.XML.Tree

2007-03-17 Thread Martin Nilsson (Opera Mini - AFK!) @ Pike (-) developers forum
Pretty high latency, I know, but this didn't became a problem until now (again): About a year ago I rewrote the Parser.XML.Tree to be much more object oriented. The major design goal was to be able to easily redefine the produced nodes in the tree. Basically you could do class Node { in