[QBS] Increasing verbosity of targetOS-based on conditions in user code

Joerg Bornemann joerg.bornemann at digia.com
Thu Jun 13 12:26:54 CEST 2013

On 13/06/2013 12:03, Oswald Buddenhagen wrote:

> however, one should consider that the filter-based approach is purely
> declarative, which facilitates tooling (as opposed to the functional
> code above).

And the big advantage of having declarative filters would be that users 
can create a special subset of boolean expressions in a point-and-click 

>> Do you plan to allow the contains() method to receive a list of
>> parameters in order to make the above even shorter, or would it be
>> possible to write something like:
>>    condition: qbs.targetOS in ["windows", "darwin"]
> targetOS will be a list once jake's changes are in. the semantics of
> 'in' on a list are blurry at best. the dedicated filter syntax seems
> less confusing to me.

It's not blurry. It's just working on keys, which is unexpected if 
you've seen useful in-operators like in Python. :)



More information about the Qbs mailing list