Maintaining compatibility with newer versions

[Nayan Deshmukh]

On Mon, Apr 13, 2020 at 7:57 AM Peter Hutterer <peter.hutterer at who-t.net> wrote:
>
> Hi Nayan,
>
> On Sun, Apr 12, 2020 at 10:28:22PM +0900, Nayan Deshmukh wrote:
> > Hi,
> >
> > I have written bindings for libevdev in rust [1].
> >
> > I am having trouble converting the event type/code enums from C to
> > rust. I want to handle the case where new event type/codes are
> > introduced in the kernel and are not yet available in the version of
> > the libevdev that the bindings are using.
> >
> > My life and code will be much easier with the assumption that new
> > event types will not be introduced and the only possibility is the
> > introduction of new event codes. Can you please shed some light on
> > this? Is this a valid assumption?
>
> while it's unlikely that new types will get introduced, it's definitely
> possible. There have been ideas floating around in the past for it, but
> nothing ever came to fruition. But still, new event types are possible.
>
I will take that possibility into account while writing the rust enums. Thanks.

Nayan
> Cheers,
>    Peter
>
> >
> > Thanks,
> > Nayan Deshmukh
> >
> > [1] https://github.com/ndesh26/evdev-rs