Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WsiSZ-0000NS-HP for pgsql-docs@arkaria.postgresql.org; Fri, 06 Jun 2014 00:56:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WsiSY-0000CD-Qe for pgsql-docs@arkaria.postgresql.org; Fri, 06 Jun 2014 00:56:42 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1WsiSX-00009W-Ff for pgsql-docs@postgresql.org; Fri, 06 Jun 2014 00:56:41 +0000 Received: from mail-wi0-x22a.google.com ([2a00:1450:400c:c05::22a]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1WsiSU-0005dC-CT for pgsql-docs@postgresql.org; Fri, 06 Jun 2014 00:56:39 +0000 Received: by mail-wi0-f170.google.com with SMTP id bs8so191888wib.1 for ; Thu, 05 Jun 2014 17:56:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wVbI8fmvRq9w17rIGn9puLMkoF79B2Ypv+2RT9O+UaI=; b=UOwLaHCE8/zOX5YQ1CajPVCTwC4kaZQOH9vWwDuYdFDT5UrixAPk2KO/9YmAz4x+RT GxSxxUQ99pwUd1YPRk4FAJLASGhar19s5a8BDpMt6lVbTH11xQYJHaXX9Lja+eBSUSxc 2LplCTdN12aSK70HaAL3t6zzLSe7h+6T/HEg0pFXVFvaSqBXHWutcgxPHvLOCnkY+/se QAxsRLvg7AeHkRwQt1p6db0XU2OGotgVRdrdFBs8h4lhnkpCznbmP5Qr/nmykjKL194S KVIIEKsz4IE8SgQMy4Tb/Qw1qpJ3g6NhpI9BIUXDPP9D5GrNr4/SA54WlL9MRIUJjthn yLXg== MIME-Version: 1.0 X-Received: by 10.194.23.135 with SMTP id m7mr1933232wjf.2.1402016195853; Thu, 05 Jun 2014 17:56:35 -0700 (PDT) Received: by 10.217.1.145 with HTTP; Thu, 5 Jun 2014 17:56:35 -0700 (PDT) In-Reply-To: References: <1402011281941-5806271.post@n5.nabble.com> <28673.1402012845@sss.pgh.pa.us> Date: Thu, 5 Jun 2014 20:56:35 -0400 Message-ID: Subject: Re: Some qualms with the current description of RegExp s,n,w modes. From: David Johnston To: Tom Lane Cc: pgsql-docs@postgresql.org Content-Type: multipart/alternative; boundary=047d7b5d5ffe52c47b04fb205519 X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org --047d7b5d5ffe52c47b04fb205519 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > > >> Or just "newline-sensitive matching" ... does "full" add anything? >> > =E2=80=8BAnd since I'm nit-picking anyway - the word "sensitive" does nothi= ng for me. Simply "newline-matching" would be sufficient, ideally. i.e., Do ". [^]" and "^$" match the newline character, or not. [w] anchor newline-matching [n] dot/inverse-bracket newline-matching [s] newline-matching These are precise, what-oriented, names compared to: [w] record mode [n] multi-line mode [s] single-line mode which are more descriptive, use-oriented, names. Use of these label sets is not mutually exclusive... David J. --047d7b5d5ffe52c47b04fb205519 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Or just "newline-sensitive matching" ... does "full" ad= d anything?

<= div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif= "> =E2=80=8BAnd since I'm nit-picking anyway - the word "sensitive&qu= ot; does nothing for me. =C2=A0Simply "newline-matching" would be= sufficient, ideally. =C2=A0i.e., Do ". [^]" and "^$" m= atch the newline character, or not.

[w] anchor newline-matching
[n] dot/inverse-bracket newline-matching
[s] newline-matching
=

These are precise, what-oriented, names compared to:

<= /div>
[w] record mode
[n] multi-line mode
[s] single-line mode

= which are more descriptive, use-oriented, names.

U= se of these label sets is not mutually exclusive...

David J.

--047d7b5d5ffe52c47b04fb205519--