Re: error with -dseparate-log-files

[David Kastrup]

Colin Hall <address@hidden> writes:

> On Tue, Aug 21, 2012 at 09:48:09AM +0100, Phil Holmes wrote:
>> ----- Original Message ----- From: "Colin Hall"
>> >
>> >Looks like there are two bugs here:
>> >
>> >1. Eluze reported that -dseparate-log-files does not work on Windows.
>> >
>> >2. Lilypond running on Windows attempted to use /dev/stderr, which is not
>> >available on the Windows platform.
>> >
>> >I see that David has opened a tracker for the code attempting to
>> >use /dev/stderr.
>> >
>> >http://code.google.com/p/lilypond/issues/detail?id=2759
>> >
>> >I'll create a tracker for the -dseparate-log-files problem.
>> >
>> 
>> I think it's the same bug.  -dsepetc. doesn't work on windows
>> because dev\stderr doesn't exist on Windows.
>
> Well, David didn't refer to the bug report from Eluze when he created
> his tracker.

Sometimes sloppiness is just sloppiness.

> I took that to mean he had identified a separate, deeper problem, and
> acted accordingly.

Never assume a deeper reason for something that can be explained by
laziness.

/dev/stderr is not supported on quite a few Unix-like systems either, so
the problem is not strictly Windows-specific.  In contrast, there are
GNU programs like gawk that interpret /dev/stderr specially internally,
so this "device" works everywhere for them, even on Windows.  Guile
doesn't do that sort of device simulation.  GNU/Linux happens to have
the device for real (and probably has had so for a long time).  But I
don't think it is part of POSIX.

-- 
David Kastrup