[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: API change with macro KEY_EVENT?
From: |
Thomas Dickey |
Subject: |
Re: API change with macro KEY_EVENT? |
Date: |
Fri, 14 Aug 2020 05:36:43 -0400 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
On Fri, Aug 14, 2020 at 09:39:31AM +0200, Dr. Werner Fink wrote:
> Hi,
>
> I've a report from our build team doing a stage test (rebuilding all tools
> with new libraries and/or compilers):
>
> | Visit https://build.opensuse.org/request/show/825926
> |
> | Dominique Leuenberger wrote in request 825926:
> |
> |
> | [ 128s] In file included from curkeys.cc:30:
> | [ 128s] curkeys.h:168:5: error: 'KEY_EVENT' was not declared in this
> scope; did you mean 'KEY_OPEN'?
> | [ 128s] 168 | { KEY_EVENT, "Event" },
> | [ 128s] | ^~~~~~~~~
> | [ 128s] | KEY_OPEN
>
> What had happen to KEY_EVENT
KEY_EVENT is/was only a possible return-value from wgetch if the key-events
feature is configured. If someone's testing for its existence (rather than
as a valid return-value), that's an api change, arguably. abi didn't change...
(key-events hasn't gotten much use anyway - developer didn't provide any
documentation or examples of use)
--
Thomas E. Dickey <dickey@invisible-island.net>
https://invisible-island.net
ftp://ftp.invisible-island.net
signature.asc
Description: PGP signature
Re: API change with macro KEY_EVENT?,
Thomas Dickey <=