[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: providing a libidn compatibility API
From: |
Simon Josefsson |
Subject: |
Re: providing a libidn compatibility API |
Date: |
Sun, 19 Feb 2017 10:11:42 +0100 |
User-agent: |
Gnus/5.130014 (Ma Gnus v0.14) Emacs/24.4 (gnu/linux) |
Nikos Mavrogiannopoulos <address@hidden> writes:
> Hi,
> What do you think of the following merge request:
> https://gitlab.com/jas/libidn2/merge_requests/4
>
> It introduces a (very-limited) compatibility API with libidn, allowing
> several applications to switch from IDNA2003 to IDNA2008 by changing
> idna.h with idn2.h.
I like the idea of a compatibility layer -- but I strongly believe we
need to keep the ^idn2_.* namespace in the shared library, everything
else will cause serious confusion in distributions when apps will be
linked to both libraries. Mapping idn_* into idn2_* calls should be
done through a header file, so which symbol is needed is decided at
compilation time.
I must admit I haven't looked at what got pulled into git later on,
still catching up on emails...
/Simon
signature.asc
Description: PGP signature
- Re: providing a libidn compatibility API, Tim Rühsen, 2017/02/07
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/10
- Re: providing a libidn compatibility API, Tim Rühsen, 2017/02/10
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/10
- Re: providing a libidn compatibility API, Tim Rühsen, 2017/02/10
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/13
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/14
- Re: providing a libidn compatibility API, Tim Ruehsen, 2017/02/14
- Re: providing a libidn compatibility API, Nikos Mavrogiannopoulos, 2017/02/14
- Re: providing a libidn compatibility API, Simon Josefsson, 2017/02/19