[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-dev] ✘INCOMPATIBLE API change -- add gnssid:svid

From: Eric S. Raymond
Subject: Re: [gpsd-dev] ✘INCOMPATIBLE API change -- add gnssid:svid
Date: Thu, 20 Sep 2018 16:19:42 -0400
User-agent: Mutt/1.9.4 (2018-02-28)

Michael J. Tubby B.Sc. MIET <address@hidden>:
> If we're doing a major version number bump, have we sorted out the
> differences in the GPSD version number and the JSON API version number
> issues that I reported about 7-8 months ago?
> From recollection there was confusion between which version number was being
> placed where and this meant that a program could not be compiled against an
> API version (for example in C with #defines for the API major/minor number)
> and check the version of the API in the JSON library.
> The issue here is that we need to be able to:
>     1. check compiled code against stated versions in (a) the API headers
> for the language and (b) the version info in the API messages
>     2. check the version of GPSD on the other side of the API
> Hence, the API needs to pass two distinct sets of version info:
>     1. API version (enumerated value)
>     2. GPSD version number sourcing the API
> I've been out of the loop for a while so not sure if this has been
> sorted.... if not then pelase can we wort it while doing a major API bump?

A good time to clear it up, yes.

The JSON should ship the JSON version.  The C and Python header files
should ship the API version.  If either shipping the other, that's
a problem
                <a href="";>Eric S. Raymond</a>

My work is funded by the Internet Civil Engineering Institute:
Please visit their site and donate: the civilization you save might be your own.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]