Re: [PATCH bpf v3] libbpf: handle symbol versioning properly for libbpf.a

[Alexei Starovoitov <ast@xxxxxx>]

On 9/30/19 9:29 AM, Yonghong Song wrote:
> +OLD_VERSION(xsk_umem__create_v0_0_2, xsk_umem__create, LIBBPF_0.0.2)
> +NEW_VERSION(xsk_umem__create_v0_0_4, xsk_umem__create, LIBBPF_0.0.4)

how this will look when yet another version of this function is 
introduced, say in 0.0.6 ?

OLD_VERSION(xsk_umem__create_v0_0_2, xsk_umem__create, LIBBPF_0.0.2)
OLD_VERSION(xsk_umem__create_v0_0_4, xsk_umem__create, LIBBPF_0.0.4)
NEW_VERSION(xsk_umem__create_v0_0_6, xsk_umem__create, LIBBPF_0.0.6)

0.0.4 will be renamed to OLD_ and the latest addition NEW_ ?
The macro name feels a bit confusing. May be instead of NEW_
call it CURRENT_ ? or DEFAULT_ ?
NEW_ will become not so 'new' few months from now.