From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from list by lists.gnu.org with archive (Exim 4.71)
	id 1Sjk37-0003pc-IF
	for mharc-grub-devel@gnu.org; Wed, 27 Jun 2012 00:40:17 -0400
Received: from eggs.gnu.org ([208.118.235.92]:41519)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rmabee@comcast.net>) id 1Sjk35-0003pW-2w
	for grub-devel@gnu.org; Wed, 27 Jun 2012 00:40:16 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rmabee@comcast.net>) id 1Sjk33-0000BC-DT
	for grub-devel@gnu.org; Wed, 27 Jun 2012 00:40:14 -0400
Received: from qmta09.westchester.pa.mail.comcast.net ([76.96.62.96]:51750)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rmabee@comcast.net>) id 1Sjk33-0000AK-9I
	for grub-devel@gnu.org; Wed, 27 Jun 2012 00:40:13 -0400
Received: from omta12.westchester.pa.mail.comcast.net ([76.96.62.44])
	by qmta09.westchester.pa.mail.comcast.net with comcast
	id TGb61j0050xGWP859GgAxY; Wed, 27 Jun 2012 04:40:10 +0000
Received: from [192.168.1.101] ([24.63.69.222])
	by omta12.westchester.pa.mail.comcast.net with comcast
	id TGg41j0034nkFao3YGg4CT; Wed, 27 Jun 2012 04:40:04 +0000
Message-ID: <4FEA8EA8.9000607@comcast.net>
Date: Wed, 27 Jun 2012 00:40:08 -0400
From: Robert Mabee <rmabee@comcast.net>
User-Agent: Mozilla/5.0 (X11; Linux i686;
	rv:12.0) Gecko/20120430 Thunderbird/12.0.1
MIME-Version: 1.0
To: grub-devel@gnu.org
Subject: Re: Release of 2.00~rc1
References: <4FE62E30.7080608@gmail.com> <4FE6C1DF.9050000@comcast.net>
	<4FE8AC8F.4010806@gmail.com> <4FE91B67.104@comcast.net>
	<4FE9227A.3010808@gmail.com>
In-Reply-To: <4FE9227A.3010808@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
	recognized.
X-Received-From: 76.96.62.96
X-BeenThere: grub-devel@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: The development of GNU GRUB <grub-devel@gnu.org>
List-Id: The development of GNU GRUB <grub-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/grub-devel>,
	<mailto:grub-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/grub-devel>
List-Post: <mailto:grub-devel@gnu.org>
List-Help: <mailto:grub-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/grub-devel>,
	<mailto:grub-devel-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jun 2012 04:40:16 -0000

On 06/25/2012 10:46 PM, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 26.06.2012 04:16, Robert Mabee wrote:
>> REG_NEWLINE causes incorrect results when a filename contains a newline,
>> both because a wild char won't match the newline, and because the generated
>> pattern anchors ^$ can match adjacent to the newline.
> Looks like you misinterpret the flags and it's actually reversed to what
> you say. Did you check that claimeed behaviour actuall occurs?
Yes, though with a different filename.
>         REG_NEWLINE
>                Match-any-character operators don't match a newline.
>
>                A nonmatching list ([^...])  not containing a newline does
> not match a newline.
>
>                Match-beginning-of-line operator (^) matches the empty
> string immediately after a newline, regardless of whether eflags, the
> execution flags of  regexec(),  con‐
>                tains REG_NOTBOL.
Those are the undesirable (in my opinion) behaviors in this case, where 
^ and $
are supplied automatically to make sure the user pattern matches the entire
filename, and everyone knows * matches all files, but newline in a filename
spoils both.