[cairo] "operator" keyword in libcairo

[Carl Worth]

On Wed, 19 Jan 2005 10:33:12 -0500, Owen Taylor wrote:
> > But "operator" really is the right word, (both mathematically and from
> > following the Porter/Duff paper).
> 
> Remember, it's only the header files. You can call the parameter
> different things in the source files and the headers if you want.

Yeah, that's what we did with the prototypes in cairo.h, and I almost
committed the same thing for cairoint.h this morning, but I ran into
the following:

	typedef struct _cairo_gstate {
	    cairo_operator_t operator;
	    /* ... */
	}

Any suggestion for that one?

Of course, just never using C++ in the implementation of cairo would
be fine by me. But I'm also not volunteering to write a win32
backend...

> (For 'class', for historical reasons we use 'klass')

How kewl. Given the choice, I'd abbreviate before misspelling. ;-)

-Carl
-------------- 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/20050119/b6ecd38c/attachment.pgp