--===============1287657938==
Content-Type: multipart/signed;
  boundary="nextPart1826606.Dq6LWNWoEa";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1826606.Dq6LWNWoEa
Content-Type: Text/Plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable

On Thursday 2 July 2009 22:15:07 Ozan =C3=87a=C4=9Flayan wrote:
> Where can I find the complete reference of the predicate rules used in
> solid device action files?

It's currently missing. And for sure it'd deserve a page on techbase.=20
Unfortunately no one stepped up for it yet, and I'm lacking the time and=20
motivation to do it myself.

The syntax is quite simple though, there's not that many constructs:
 * "[ termA OR termB ]" or "[ termA AND termB ]" for logical combinations;
 * "Interface.property =3D=3D value" to match a given value for a given pro=
perty=20
if the given Interface is supported by the device;
 * "Interface.property & value" to match a given value but using the binary=
=20
AND operator (checking if property has the value flag set).

And then the | operator that you ask for below:

> I'm seeing different usages of different
> operators in many projects but I can't get the expected results when I
> evaluate them using solid-hardware. One such example is the pipe operator:
>
> $ solid-hardware query "foo.bar =3D=3D 'PropertyX|PropertyY'"

Those are enums/flags values, so the syntax closely follow the C++ one by=20
using a binary OR operator (pipe operator in C/C++).

> looking at it, one can think that | acts like an OR operator between
> PropertyX and PropertyY but that doesn't work in that way, so I wonder
> what's the aim of that operator.

It exactly acts like an OR operator, but the binary one so foo.bar =3D=3D '=
X|Y'=20
means that foo.bar should have both X and Y.

Regards.
=2D-=20
K=C3=A9vin 'ervin' Ottens, http://ervin.ipsquad.net
"Ni le ma=C3=AEtre sans disciple, Ni le disciple sans ma=C3=AEtre,
Ne font reculer l'ignorance."

--nextPart1826606.Dq6LWNWoEa
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkpT5xMACgkQB0u7y43syeK6GQCgiAZOSWOTabUjJVTSQqpLm70V
6D0AoI0WXtOSDQCpV71g4nxQ9dJPJR8b
=Cdhj
-----END PGP SIGNATURE-----

--nextPart1826606.Dq6LWNWoEa--

--===============1287657938==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-hardware-devel mailing list
Kde-hardware-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-hardware-devel

--===============1287657938==--