Bruno Le Floch

Even that is too slow in a normal TeX run, but we could add something like that to the l3debug code.

Regardless of the outcome of this discussion, it will be useful to document in xparse.pdf how to reproduce the behaviour of \verb using \NewDocumentCommand.

I would suggest just wrapping every character in an hbox. It seems to work reasonably well, but I didn't test extensively. \RequirePackage{xparse} \ExplSyntaxOn \NewDocumentCommand{\myverb}{v}{\texttt{\str_map_function:nN{#1}\hbox:n}} \ExplSyntaxOff \documentclass{article} \usepackage[T1]{fontenc} \begin{document} \verb|a--b ---c...

Ok, second attempt (the `v` arg keeps active chars as is): insert `\kern 0pt\relax` before all non-active chars. ``` \RequirePackage{xparse} \ExplSyntaxOn \tl_new:N \l__myverb_tl \cs_new:Npn \__myverb:n #1 { \token_if_active:NF #1 {...

Actually your sentence seems to be not quite right: the test gives false when the expression evaluates to `0` or `-0`, and true when the expression gives anything else (including...

I think it is possible by using the table of precedences - 16: Function calls. - 13/14: Binary `**` and `^` (right to left). - 12: Unary `+`, `-`, `!`...

Profiling expandable commands may be possible, by abusing the fact that the buffer for the log file is finite. Basically, go to scrollmode, write some marker to the log file,...

Clearly a bug. As Joseph says two characters are tokenized (the same happens with `\foo= \bar`), but only because the first is a space (in `\foo=?\bar` the backslash is not...

Thanks Joseph. This is not a problem, because tokens are looked at one by one, and if the regex tests decide they are done, then they just call `\peek_analysis_map_break:` and...

Sadly no, the issue is not fixed. The regex code reads one token too many, and the peek code used to read ahead a second token when seeing a space...