X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/05b55f06fa36f45a80231bd43a9e1503c445ca2a..029a6b72e72d0c4da8c3ef95e42a8d8caae6687f:/doc/todo/nested_preprocessor_directives.mdwn?ds=sidebyside diff --git a/doc/todo/nested_preprocessor_directives.mdwn b/doc/todo/nested_preprocessor_directives.mdwn index 1d44cea88..3094e0899 100644 --- a/doc/todo/nested_preprocessor_directives.mdwn +++ b/doc/todo/nested_preprocessor_directives.mdwn @@ -24,11 +24,25 @@ nesting, a new syntax would be needed. Maybe something xml-like? >> In the meantime, this is an interesting approach: >> >> ->> \[[!directive text=<> \[[!directive text=\<\> ... ->> <> FOO]] >> >> Since that's implemented, I will probably just merge it, >> once I satisfy myself it doesn't blow up in any edge cases. >> (It also adds triple single quotes as a third, distinct type of quotes, >> which feels a bit redundant given the here docs.) --[[Joey]] +>> +>> Hmm, that patch changes a `m///sgx` to a `m///msgx`. Meaning +>> that any '^' or '$' inside the regexp will change behavior from matching +>> the start/end of string to matching the start/end of individual lines +>> within the string. And there is one legacy '$' which must then +>> change behavior; the "delimiter to next param". +>> +>> So, I'm not sure what behavior that will cause, but I suspect it will +>> be a bug. Unless the `\s+|$' already stops matching at a newline within +>> the string like it's whitespace. That needs more alalysis. +>> Update: seems it does, I'm fairly satisfied that is not a bug. +>> +>> Also, the patch seems incomplete, only patching the first regexp +>> but not the other two in the same function, which also are quoting-aware. --[[Joey]]