From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 79613138010 for ; Mon, 1 Oct 2012 16:33:56 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8874CE039A; Mon, 1 Oct 2012 16:33:45 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 52145E039A for ; Mon, 1 Oct 2012 16:33:45 +0000 (UTC) Received: from [192.168.26.5] (ip98-164-193-252.oc.oc.cox.net [98.164.193.252]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 9B78B33C6B6 for ; Mon, 1 Oct 2012 16:33:44 +0000 (UTC) Message-ID: <5069C5E7.3020604@gentoo.org> Date: Mon, 01 Oct 2012 09:33:43 -0700 From: Zac Medico User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:15.0) Gecko/20120901 Thunderbird/15.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Package Manager Specification discussions X-BeenThere: gentoo-pms@gentoo.org X-BeenThere: gentoo-pms@lists.gentoo.org Reply-To: gentoo-pms@lists.gentoo.org MIME-Version: 1.0 To: gentoo-pms@lists.gentoo.org Subject: Re: [gentoo-pms] [PATCH] EAPI must be at least a single char. References: <1348993716-27744-1-git-send-email-ferringb@gmail.com> <20584.3387.660954.8184@a1i15.kph.uni-mainz.de> <20120930194455.GB2180@localhost> <5068A308.3090303@gentoo.org> <20120930222235.GH2180@localhost> <5068E2E0.8080803@gentoo.org> <20585.17179.531266.341712@a1i15.kph.uni-mainz.de> In-Reply-To: <20585.17179.531266.341712@a1i15.kph.uni-mainz.de> X-Enigmail-Version: 1.4.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 48b61453-0f16-43c4-be71-addefe215130 X-Archives-Hash: 003bc3bb84118587b7d4907275b43635 On 10/01/2012 12:15 AM, Ulrich Mueller wrote: >>>>>> On Sun, 30 Sep 2012, Zac Medico wrote: > >> Still, I'd be in favor of changing the regex to match practically >> anything that looks like an EAPI assignment, regardless of the >> validity of the EAPI value. > > I don't believe that this is possible. You'll never be able to match > everyting that it valid bash syntax, other than by parsing it with > bash itself. Which is what we wanted to avoid, in the first place. > > (( $'\x45\x41\x50\x49' = 4 + 1 )) The package manager wouldn't need any more knowledge of bash syntax than it currently has. All of the implementation details would be the same as they are now. The only difference would be that the regex would return a match in _more_ cases. I think that this would be preferable to Brian's suggestion to make the regex fail to match an empty EAPI setting (which would return a match in _fewer_ cases). -- Thanks, Zac