Testing output from each backend (was: [cairo] State of Win32 backend?)

Carl Worth cworth at redhat.com
Tue May 10 20:29:39 PDT 2005

On Tue, 10 May 2005 08:27:38 -0400, Owen Taylor wrote:
> On Tue, 2005-05-10 at 10:33 +0300, Tor Lillqvist wrote:
> >  > The only correct way to do this operation under Unix is to use
> >  > dup2(), so unless that works under Windows (seems unlikely)
> > 
> > Yes, dup2() does work on Windows. (It's handled by the C library, not
> > the OS, but it does works like on Unix.)
> As long as it can be used to redirect stderr by 
> close(2), dup2(otherfd,2), it can be used.

That's all moot now, as I've removed the writing of stderr. I wasn't
really doing this for the sake of any error messages from cairo, (it's
pretty silent already---maybe too silent).

I was really just trying to avoid abstraction leakage withing the
cairo/test files. But writing to stderr was causing too many problems,
so I've switched it all to use a new cairo_test_log function rather
than fprintf(stderr,...).


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/cairo/attachments/20050510/dc343f93/attachment.pgp

More information about the cairo mailing list