On 2013-12-14 15:53, Steven Schveighoffer wrote:

> I realize this is really old, and I sort of dropped off the D cliff
> because all of a sudden I had 0 extra time.
>
> But I am going to get back into working on this (if it's still an issue,
> I still need to peruse the NG completely to see what has happened in the
> last few months).

Yeah, it still need to be replaced. In this case you can have a look at the review queue to see what's being worked on:

http://wiki.dlang.org/Review_Queue

-- 
/Jacob Carlborg

On Saturday, 14 December 2013 at 15:16:50 UTC, Jacob Carlborg wrote:
> On 2013-12-14 15:53, Steven Schveighoffer wrote:
>
>> I realize this is really old, and I sort of dropped off the D cliff
>> because all of a sudden I had 0 extra time.
>>
>> But I am going to get back into working on this (if it's still an issue,
>> I still need to peruse the NG completely to see what has happened in the
>> last few months).
>
> Yeah, it still need to be replaced. In this case you can have a look at the review queue to see what's being worked on:
>
> http://wiki.dlang.org/Review_Queue


SINK, TAP
---------


https://github.com/schveiguy/phobos/blob/new-io/std/io.d

What about adding a single property named sink or tap depending
on how you want the chain to be. That could be either a struct or
a class. Each sink would provide another interface.


struct/class ArchiveWriter(SINK)
{
	@property sink		//pointer to sink
}



writer.sink.sink.sink
arch.sink.sink.sink.open("filename");


ArchiveReader!(InputStream) * reader;


"Warning: As usual I don't know what I'm talking about."

On Wed, 16 Apr 2014 12:09:49 -0400, sclytrack <sclytrack@fake.com> wrote:

> On Saturday, 14 December 2013 at 15:16:50 UTC, Jacob Carlborg wrote:
>> On 2013-12-14 15:53, Steven Schveighoffer wrote:
>>
>>> I realize this is really old, and I sort of dropped off the D cliff
>>> because all of a sudden I had 0 extra time.
>>>
>>> But I am going to get back into working on this (if it's still an issue,
>>> I still need to peruse the NG completely to see what has happened in the
>>> last few months).
>>
>> Yeah, it still need to be replaced. In this case you can have a look at the review queue to see what's being worked on:
>>
>> http://wiki.dlang.org/Review_Queue
>
>
> SINK, TAP
> ---------
>
>
> https://github.com/schveiguy/phobos/blob/new-io/std/io.d
>
> What about adding a single property named sink or tap depending
> on how you want the chain to be. That could be either a struct or
> a class. Each sink would provide another interface.

Chaining i/o objects is something I have yet to tackle. I have ideas, but I'll wait until I have posted some updated code (hopefully soon). I want it to work like ranges/unix pipes.

The single most difficult thing is making it drop-in-replacement for std.stdio.File. But I'm close...

-Steve

While waiting for the new stream I wrote myself a stream for file io only.
http://dpaste.dzfl.pl/bc470f96b357

Hope it helps your work somehow. Maybe at least the unittests are helpful?

On Wed, 28 May 2014 06:28:25 -0400, Tero <sghtr@naesaatbh.invalid> wrote:

> While waiting for the new stream I wrote myself a stream for file io only.
> http://dpaste.dzfl.pl/bc470f96b357
>
> Hope it helps your work somehow. Maybe at least the unittests are helpful?

Cool. I actually have made some progress, I have a new-io3 branch on github. Nothing finalized yet, but it does do basic input and output in all encodings.

I will probably rewrite the entire API at least twice before it's ready (in fact, already doing that), but the guts will be similar.

I will take a look at your code to see if there's anything I can use, thanks!

-Steve

Just noticed, the paste was screwed. Had a weird character in a comment which seemed to confuse dpaste.

Here's the full code:
http://dpaste.dzfl.pl/fc2073c19e7d

On Thursday, 29 May 2014 at 03:43:32 UTC, Steven Schveighoffer wrote:
> On Wed, 28 May 2014 06:28:25 -0400, Tero <sghtr@naesaatbh.invalid> wrote:
>
>> While waiting for the new stream I wrote myself a stream for file io only.
>> http://dpaste.dzfl.pl/bc470f96b357
>>
>> Hope it helps your work somehow. Maybe at least the unittests are helpful?
>
> Cool. I actually have made some progress, I have a new-io3 branch on github. Nothing finalized yet, but it does do basic input and output in all encodings.
>
> I will probably rewrite the entire API at least twice before it's ready (in fact, already doing that), but the guts will be similar.
>
> I will take a look at your code to see if there's anything I can use, thanks!
>
> -Steve