[xcvb-devel] run-program/process-output-stream

[Faré]

> Ah, I was just curious, because in perl, this code:
>
> @foo = `cat file`;
>
> (which is similar in concept to run-program/process-output-lines with the
> 'slurp-stream-lines output processor) preserves the newline for each line.
>
I am aware of that. I wanted some small code use trivial Lisp functionality,
so I use read-line that behaves like this.

> I'm not advocating change, but I was surprised by the newline difference
> between the two stream processors.
>
> Also, would you prefer that I added docstrings for how to use these
> functions? Or just commented above them their use/edge cases and whatnot?
>
This indeed deserves to be documented, in a comment if not in a
docstring. I have no preference.

As I realize it has to deal with portability, I'm considering having
master either depend on driver, or be merged into driver so that it
remains a single file. What do you think?

> BTW, I got hu.dwim.stefil working (and the required externals installed in
> the same manner as the others) and have started writing a basic unit-test
> suite for run-program/*. I need to figure out how to test for signaled
> conditions and other things too, but I'm making progress.
>
Excellent. Note that under windows, things are subtly different. Sigh.

Having to deal with PATHs under Windows is the promise of HELL.

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
Long live consumership, which is individual and responsible choice!
Down with citizenship, which is collective and irresponsible choice!