[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: providing a libidn compatibility API
From: |
Nikos Mavrogiannopoulos |
Subject: |
Re: providing a libidn compatibility API |
Date: |
Thu, 26 Jan 2017 14:58:33 +0100 |
On Thu, Jan 26, 2017 at 2:46 PM, Tim Ruehsen <address@hidden> wrote:
>> Cool. Is the idn2_* intentional? I was thinking of providing
>> compatibility in a way that sources do not need to be changed at all
>> (i.e., provide an idna.h, and compatibility idna_* functions - which
>> could also be wrappers). It would be very nice if we could compile
>> programs that use libidn, using libidn2 without any changes (at least
>> for the majority of them).
> The naming is intentional because
> 1. What about apps providing idna2003 *and* idna2008 (libidn and libidn2) ?
> 2. idn2_ is the namespace for libidn2 (mainly because of 1)
> We could use a define being set before #include <idn2.h>, e.g.
> IDN2_LIBIDN_API.
> WDYT ?
I'd expect the idna2003 + idna2008 apps to be rare, but you got a
point. I think the define approach is reasonable.
regards,
Nikos
- providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/01/26
- Re: providing a libidn compatibility API, Tim Ruehsen, 2017/01/26
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/01/26
- Re: providing a libidn compatibility API, Tim Ruehsen, 2017/01/27
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/01/28
- Re: providing a libidn compatibility API, Tim Rühsen, 2017/01/28
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/01/29
- Re: providing a libidn compatibility API, Tim Ruehsen, 2017/01/27
- Re: providing a libidn compatibility API, Tim Ruehsen, 2017/01/27