Class definitions behavior

[Adam Moffett]

On 9/8/2010 3:59 PM, Simon Hobson wrote:
> Adam Moffett wrote:
>
>> Thanks Simon.  If I understand you correctly then a client can belong 
>> to many classes.
>
> Yes
>
>> In a pool let's say I allow one class and deny another like so:
>> pool {
>>   allow members of "foo";
>>   deny members of "bar";
>>   range x.x.x.x y.y.y.y;
>> }
>>
>> If a client belongs to both foo and bar will he be allowed or denied?
>> I think you're going to tell me that the answer is "allowed" because 
>> that's what I think I'm seeing.
>
> Actually my answer is "dunno" ! Allow and Deny aren't done as a list, 
> and the results aren't as intuitive as perhaps they could be in 
> hindsight - but I assume the devs had a reason to do it as they did.
>
> General advice is to avoid mixing allow and deny clauses.
>

LOL that's great.  How about this:  I can avoid the issue with a more 
complex match, but It complains at me if I have more than one match 
clause in a class.  Is there a syntax for "and" and "or" in a match?  
Anyone?