Friday, June 21, 2002 John Culleton wrote:
JC> In my very humble opinion this is a big part of the problem with tools JC> such as XML and its children. Using two tags where one will do is just JC> excessive clutter, and ends up with lines like JC> \stopsubusubsection \stopsubsection \stopsection \stopchapter JC> .... which is all superfluous code and offers the chance for keying errors on JC> every tag. The computer is smart enough to know that a \chapter head JC> terminates all previous subordinate levels. And the person reading the code JC> is smart enough too. I see no virtue in this proposal. I thought I pointed out some of the pluses ... do you have any specific idea to counter to any of the pluses (apart from the folding thingie which is just a bonus)? JC> No matter how elegant the code looks, in fact it is just a means to an end, JC> and the end is a publication, and all those meaningless stop tabs won't JC> afffect the final document in any case. Actually it does, in those cases when you want to do something at the END of all section blocks of the same type (e.g. a local ToC) --just put the appropriate code in the \stop<sectionblock> hook. Other aspects of how my idea CAN affect the final result of the document is provided in my original post. -- Giuseppe "Oblomov" Bilotta
