> On 8 Mar 2021, at 3:36 pm, Jeffrey Walton via Cocoa-dev
> wrote:
>
> Tee(1) is not writing the file for him, and I can confirm the
> behavior. Here's how it is being used:
>
>./cryptest-ios.sh 2>&1 | tee cryptest-ios.txt
Hey Jeff,
I recall encountering a similar problem a few months ago
On 9 Mar 2021, at 12:10, Jean-Daniel wrote:
If I had to write a new software that need read/write functions today,
I would go for a modern async API, like dispatch_io.
This came up while trying to generalize a few things I have that
basically transform data, but where size is unknown, and the
> Le 9 mars 2021 à 09:07, Allan Odgaard via Cocoa-dev
> a écrit :
>
> We currently have two different systems that can’t easily be bridged,
> effectively doing the same thing, but supporting different sources:
>
> NSStream can work with files, data, and network streams (created by
> NSURLSe
We currently have two different systems that can’t easily be bridged,
effectively doing the same thing, but supporting different sources:
NSStream can work with files, data, and network streams (created by
NSURLSession and other high-level API).
NSFileHandle can work with files, pipes, stdin/
