On Wed, Nov 9, 2016 at 8:30 AM, Michael Orlitzky <m...@gentoo.org> wrote:
> On 11/08/2016 10:47 AM, Michał Górny wrote:
>>
>> Strictly speaking, we don't have to since the lexing should be
>> predictable enough. Of course, mistakes like missing version following
>> the operator would result in curious errors.
>>
>> The major problem with spaces I see is that it means we end up having
>> an additional [use] block floating following them.
>>
>
> I was also thinking that the logical operators could be infix, and then
> you need the commas to avoid precedence issues with the implicit-and,
> which is written " ".
Commas and spaces can be made optional if we allow the following
tokens to be the delimiter itself. Grouping and use of white space
can be optionally used in cases where operators would collide, most
especially after :=.
A valid package name entry also signals end of the rules for the previous entry.
Also, precedence issues and confusions can be avoid by relying on more
explicit grouping like () and {}, instead of &&, ||, & and |.
> The [use] blocks could be moved next to the
> package name I guess.
It can actually be allowed to be placed anywhere if we don't use []
for condition grouping, and just use it for the use block.
--
konsolebox
