Encoded filenames

[Matthias Andree]

David Relson <relson at osagesoftware.com> writes:

> This is not recursion.  Recursion would involve text_decode() being
> called from within text_decode().  We have the possibility of a
> second (improper) call.  

It depends on your definition for "recursion" if it is. Given that it
feeds its own output back as input can be called recursion, looping, or
similar.

> Calling text_decode earlier requires matching the RFC-2047 pattern.

Yup.

> As pattern matching is a lexer responsibility, doing it earlier is
> wrong.  If it _really_ mattered (which I doubt), a lexer mode (flag)
> could be used.  Setting it upon calling text_decode() and clearing it
> upon seeing a new header line might work.

There can be more than one encoded work on a header line.

-- 
Matthias Andree