On 07/10/2011 10:36 PM, David Bremner wrote: >> This suggests to me that we may need to be bumping the SONAME when the >> query string format changes, no? > > If we follow the same rules as with symbols, then only when it breaks > backwards compatability.
Right, but what breaks backwards compatibility in a string-based indexer?
If the query "foo bar:baz" is interpreted as a search for two separate
simple strings, and then an update treats the "bar:" suffix specially,
is that backwards-incompatible because the semantics of the identical
search change?
The only way i can currently imagine "backwards compatibility" is if
version X has a set of query strings which all return some kind of "not
implemented" error value, and then version X+1 returns a legitimate
response for some subset of those same query strings.
Otherwise, each change in query string syntax actively modifies (in a
non-backwards-compatible way) the semantics of some part of the interface.
Is there some other way to view this distinction?
--dkg
signature.asc
Description: OpenPGP digital signature
_______________________________________________ notmuch mailing list [email protected] http://notmuchmail.org/mailman/listinfo/notmuch
