> WG21 is thinking about standardising a native_handle_type



LEWGi looked at this in Cologne and said that they don’t want it, so I’m not sure it’s appropriate to bug WG14 at this time: http://wiki.edg.com/bin/view/Wg21cologne2019/P1759



[cid:image001.png_at_[hidden]]


> That means that the implementation does whatever is necessary to make it work, for some unspecified meaning of "work".



Note also that the *existence* of such members is implementation defined, so an implementation can define that they don’t exist.



Billy3



________________________________
From: Liaison <liaison-bounces_at_[hidden]> on behalf of pete--- via Liaison <liaison_at_[hidden]>
Sent: Monday, August 19, 2019 9:58:47 AM
To: liaison_at_[hidden] <liaison_at_[hidden]>
Cc: pete_at_[hidden] <pete_at_[hidden]>
Subject: Re: [wg14/wg21 liaison] Fwd: native_handle_type

On Aug 19, 2019, at 12:08 PM, Niall Douglas via Liaison <liaison_at_[hidden]> wrote:
>
> There is precedent here. You can ask POSIX what kind of inode a file
> descriptor refers to. Same goes here for native handle type, which
> similarly refers to some implementation-defined-structure-elsewhere.
> Indeed, as you may have noticed in my forwarded message to WG14, one
> could even use mode_t as the union discriminant on POSIX platforms.
>

Let me ask you again a question that you elided when you quoted me:

If the standard adds support for determining the type (for whatever meaning of “type” is involved here), what then? What can you do **portably** that you can’t do **portably** without that information?

  -- Pete
Roundhouse Consulting, Ltd.


_______________________________________________
Liaison mailing list
Liaison_at_[hidden]
Subscription: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.isocpp.org%2Fmailman%2Flistinfo.cgi%2Fliaison&amp;data=02%7C01%7Cbion%40microsoft.com%7C9123b70ecc8d4e85f2c908d724c68493%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637018307362235783&amp;sdata=7z4XaFIjjZRhhDQiqakJ%2F5YUV9P5vNpHyVtu0fEZxEU%3D&amp;reserved=0
Link to this post: https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.isocpp.org%2Fliaison%2F2019%2F08%2F0037.php&amp;data=02%7C01%7Cbion%40microsoft.com%7C9123b70ecc8d4e85f2c908d724c68493%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637018307362245779&amp;sdata=ReSu1TaviaEHz5RVyY3CBVsIICbmWd3lX2Oz%2BAb9Fb4%3D&amp;reserved=0