RE: CVS Feature Branch - version - cannot write to stdout

[Conrad T. Pino]

Sorry for the delay.  I've been traveling
and I'm still getting caught up.

> From: Mark D. Baushke
> 
> > > Hmmm... I wish I had a better #define to use to control this behavior...
> > > I suspect it may not be a problem in a cygwin environment, but I could
> > > be wrong.
> > 
> > Why not create a specific #define for this purpose?
> 
> I would not object to that approach.

That's wonderful and I'm sorry for the lack of clarity.  My intent
is to encourage you to use a specific purpose #define and since I'm
not up to speed on the code and don't have time to get there, I have
no other opinion other than to encourage doing what you really want.

> Hmmm... I susepect folks will not like us much should cvs be compiled in
> such other environment and not work properly as a result...

Agreed.

> If we use a special-purpose define for this, then that would be a fine
> idea. Otherwise, we may have other platforms that have similar problems
> and it may be useful to have a logical expression of exceptions... (I do
> not feel very strongly about it.)

No opinion other than please do what's best in your eyes.

> Actually, I think the select would be a good idea in the cases where
> stdout is a socket, so we may want to just add a bit more glue in the
> error condition... something like this perhaps?

This is beyond my knowledge area and any opinion I might render is
essentially meaningless.  I'm dropping out of this topic.

>       -- Mark

Conrad