Date: Mon, 02 Dec 2019 07:17:31 -0800
On Sunday, 1 December 2019 10:41:00 PST Lyberta via Std-Proposals wrote:
> connor horman via Std-Proposals:
> > I am working on a library in C++ that has IO Capabilities, and as part of
> > the library, I define a couple of named requirements that types being
> > written or read “raw”
>
> Obvious note that this makes data non-portable and only useful for
> inter-process communication on the same ABI.
Since inter-process communication in the same ABI is permitted, why is intra-
process communication forbidden?
> connor horman via Std-Proposals:
> > I am working on a library in C++ that has IO Capabilities, and as part of
> > the library, I define a couple of named requirements that types being
> > written or read “raw”
>
> Obvious note that this makes data non-portable and only useful for
> inter-process communication on the same ABI.
Since inter-process communication in the same ABI is permitted, why is intra-
process communication forbidden?
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel System Software Products
Received on 2019-12-02 09:20:01