Displaying 2 results from an estimated 2 matches for "allow_flag".
Did you mean:
allow_flags
2019 Aug 15
2
Re: [PATCH libnbd v2 10/10] generator: Check requirements for BytesPersistIn/Out and completion callbacks.
On 8/15/19 4:56 AM, Richard W.M. Jones wrote:
> ---
> generator/generator | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/generator/generator b/generator/generator
> index 1252bdb..13cb0b9 100755
> --- a/generator/generator
> +++ b/generator/generator
> @@ -3121,6 +3121,31 @@ let () =
> failwithf "%s: first_version
2019 Aug 15
0
Re: [PATCH libnbd v2 10/10] generator: Check requirements for BytesPersistIn/Out and completion callbacks.
...ODO, I think we can deal with
them by adding variants at a later date.
For example we wanted some "allow" flags for nbd_connect_uri, but
didn't really come to a conclusion about how to do that right now.
However in future we could do it by either adding
nbd_connect_uri_allow (..., allow_flags);
or (probably my preferred choice) using ELF symbol versions.
Are there other libraries apart from glibc where they are using ELF
symbol versioning to replace APIs? AIUI if done carefully it doesn't
need to lead to API breaks, because as with nbdkit we can require
callers to opt in to the...