Fwd: Re: linecut (warnocked?)

[Steven Schubiger]

----- Forwarded message from Jim Meyering <address@hidden> -----

Date: Fri, 19 Oct 2007 23:50:58 +0200
From: Jim Meyering <address@hidden>
To: Steven Schubiger <address@hidden>
Subject: Re: linecut (warnocked?)

Steven Schubiger <address@hidden> wrote:

> Jim Meyering <address@hidden> wrote:
>
>> If you want to get something "out there" soon,
>> doing it as a separate tool initially would be
>> a good idea.  That wouldn't keep you from proposing
>> it again, later.
>
> I'm inclined to think we should do it right before I release again.
>
>> As spec'd, it looks like a very challenging project.
>> Are you close to completing it?
>
> Yes, pretty close (if you subtract documentation et al).
>
> elide_lines_seekable() has been written from "scratch" and works
> the same for input from a pipe or file stream (no *alloc() overhead).

Good!
So it copies all input to a temporary file
when it's from a pipe?

> The parsing of the current parameters is fully functionable, which
> results in --range supporting N, -N & +N combinations.
>
> Line numbering is similar to cat, i.e. `linecut --range 1,-1 --number
> <file>` is exactly the same as `cat -n <file>` (proved via `diff -u`).
>
> So, I'm looking for a bit of advice concerning data types, eventual
> efficiency hacks and overall implementation improvement.

IMHO, you'll get good feedback (more volume and quicker)
if you post to the list and ask.

----- End forwarded message -----

linecut.c
Description: Text Data