Re: @-commands with global effects in raw blocks

[Dumas Patrice]

On Sun, Jan 20, 2013 at 11:09:35PM +0000, Karl Berry wrote:
> [Oops, think the mail got messed up, sorry.]
> 
>     Subject: @-commands with global effects in raw blocks
> 
> It's not feasible to just "tokenize" the raw blocks and avoid
> actually executing them until and unless they are output?  So that
> @anchor or whatever inside @tex has no effect when outputting HTML?

Currently the tree is not only the result of tokenization of the input.
There are already some analysis of the tree.  Some directly when doing
the tree (such as adding the information about current clickstyle to
click), some right after doing the tree, before converting.  Analysis
that  should be independent of the output is done on the tree or on 
selected commands of the tree, collected during the parsing.  For
example, all that relates to cross references is done on 
the tree before doing the actual outputting, such as veryfying that 
internal refs are correct, associating index entries, floats...  
Some @-commands also are gathered such that it is easy to go through 
them without having to go through the whole tree.

Many things are done only when outputting, sure.  I think it is better
to keep doing all that is done on the tree instead of waiting for the
output.  What could be done, however, would be to refrain from doing
anything that impacts on the whole document when in raw blocks.

Should I do that?

-- 
Pat