[cairo] "operator" keyword in libcairo

Stuart Parmenter stuartp at gmail.com
Wed Dec 29 11:07:31 PST 2004

The problem is that the GDI+ backend code needs the cairoint code to
not use operator anywhere.  I never checked in that patch cause keith
and carl didn't really want it, but it needs to go in at some point to
allow backends to ever be written using C++.


On Wed, 29 Dec 2004 08:53:40 -0800, Ned Konz <ned at squeakland.org> wrote:
> On Wednesday 29 December 2004 8:46 am, Chris wrote:
> > > > Operator is a keyword in the Microsoft compiler and causes a lot of
> > > > pain when trying to compile over there.  I'm going to rename them to
> > > > "op" or something and see how it goes from there.
> > >
> > > It shouldn't be a keyword in a C compiler (though of course it is in
> > > C++), should it? Do they also reserve new, delete, etc.?
> >
> > I found the issue with this.  It's "cairo_gdip_font.cpp" which I don't
> > need to compile but it does use the "operator" keyword and it's a C++
> > file.
> Well, sure. But then it's not going to use 'operator' as a variable name in
> that file. I still don't understand the problem. Aren't the uses of
> 'operator' as a variable name just in the C files? You compile the C files
> with a C compiler and the C++ files with a C++ compiler.
> --
> Ned Konz
> http://bike-nomad.com/squeak/
> _______________________________________________
> cairo mailing list
> cairo at cairographics.org
> http://lists.freedesktop.org/mailman/listinfo/cairo

More information about the cairo mailing list