Idea: add "optional" in the DB.

[remicollet]

This could simplify some tests.
(of course only for "really" optional, not those related to OS or to external library version)

[llaville]

I'm thinking about a concept, that will solve only the unit tests, but allow to solve platform conflicts.

Availalble on Linux, but not on Windows (see sphinx extension #174 (comment)), or depending of a PHP build conf (see redis extension #174 (comment)).

And also #185, and probably more ...

[llaville]

Optional elements WILL NOT be solved by solution (see #191 (comment)) that will fixed only library version condition.

[llaville]

No solution for 4.2.0; will be delay to another release

[llaville]

Will be incuded in new project php-compatinfo-db. See announcement in #208 (comment)

[llaville]

Use of external project is considered as API BC break, so it won't be included in a 4.x series. Will be only available for 5.0

[llaville]

Feature was introduced in php-compatinfo-db. See llaville/php-compatinfo-db@dde2051
Only constants are supported, and cURL extension referenced these first optional constants. See llaville/php-compatinfo-db@7e1beec

TestCase should, and will be clean-up in next days

[llaville]

Communications continue on php-compatinfo-db project / issue