W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2003

RE: MS-FO-LC1-047: 7.5.2 fn:matches

From: Michael Rys <mrys@microsoft.com>
Date: Thu, 3 Jul 2003 01:58:54 -0700
Message-ID: <5C39F806F9939046B4B1AFE652500A3A05C2D9A7@RED-MSG-10.redmond.corp.microsoft.com>
To: "Liam Quin" <liam@w3.org>, "Jeni Tennison" <jeni@jenitennison.com>
Cc: "Kay, Michael" <Michael.Kay@softwareag.com>, <public-qt-comments@w3.org>

As Mike pointed out, 'm' is the same as //m in Perl. I just find the term "multi-line" misleading since I (and others) read it as spanning more than one line.

Best regards
Michael

> -----Original Message-----
> From: Liam Quin [mailto:liam@w3.org]
> Sent: Wednesday, July 02, 2003 8:03 AM
> To: Jeni Tennison
> Cc: Michael Rys; Kay, Michael; public-qt-comments@w3.org
> Subject: Re: MS-FO-LC1-047: 7.5.2 fn:matches
> 
> On Wed, Jul 02, 2003 at 10:05:20AM +0100, Jeni Tennison wrote:
> > The first example:
> >   fn:matches(., "Kaum.*krähen")
> > is in string mode, so the metacharacter . matches any character
> > whatsoever, including newline (Hx0A) characters.
> [...]
> 
> > The second example:
> >
> >   fn:matches(., "Kaum.*krähen", 'm')
> >
> > is in multiline mode, so the metacharacter . matches any character
> > aside from newline (Hx0A) characters.
> 
> This seems to be exactly the opposite of the "m" modifier in Perl 5.
> Is there a reason for this incompatibility?  It's very confusing.
> 
> If there's a de facto standard for modifying regexp's for multiline
> matches, it's surely Perl.
> 
> Liam
> 
> --
> Liam Quin, W3C XML Activity Lead, liam@w3.org,
> http://www.w3.org/People/Quin/
Received on Thursday, 3 July 2003 04:59:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:56:48 UTC