## LATEX-L@LISTSERV.UNI-HEIDELBERG.DE

#### View:

 Message: [ First | Previous | Next | Last ] By Topic: [ First | Previous | Next | Last ] By Author: [ First | Previous | Next | Last ] Font: Monospaced Font

Subject:

Re: Strings, and regular expressions

From:

Date:

Mon, 10 Oct 2011 21:46:25 +0200

Content-Type:

text/plain

Parts/Attachments:

 text/plain (43 lines)
 Hi Bruno, a few comments on "random" parts of your message > - Some day I may add printf-like string formatting. Is that useful? I would think so. anything with input output formatting benefits from this. It is not a primary typesetting function but ... ;-) > - Newlines. Currently, "." matches every character; in perl and PCRE > it should not match new lines. As you know, the situation with new > lines in TeX is a little bit odd, since they are converted to the > \endlinechar upon reading, and normally not tokenized, simply giving > rise to a space or a \par. Should we still decide that "." does not > match the CR nor LF characters? Or should it simply no match the > \endlinechar? in my opinion we should accept that TeX strings do not have the notion of newlines thus one can't match against them > > - I had the idea of providing # as a shorthand for .*? (arbitrary > sequence of characters, lazy), mimicking what TeX does when finding a > macro parameter. Is it useful? don't think this requires adding an additional shorthand which is non-standard. > - Same question for caseless matching, and for look-ahead/look-behind > assertions. personally (in other languages) I alway find it useful to be able to match caseless (as an option). But then this requires an understanding on what is "case". Whether that is however important enough to go some length ... dunno > Comments, feature requests, bug reports etc. are all highly welcome. > Thanks for reading so far :). I did ... read that far ;-) cheers frank