Bug 9774 - Xrandr.h uses C++ keyword "delete" as variable name
Summary: Xrandr.h uses C++ keyword "delete" as variable name
Status: RESOLVED DUPLICATE of bug 10046
Alias: None
Product: xorg
Classification: Unclassified
Component: Protocol/Core (show other bugs)
Version: git
Hardware: Other All
: high major
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-26 15:24 UTC by Boris
Modified: 2007-02-20 13:18 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Boris 2007-01-26 15:24:32 UTC
When compiling the latest git with the xrandr library, The XServer compiles without any problems. When another application attempts to use the Xrandr.h file, It always displays this error. (example kde)

-DQT_NO_TRANSLATION -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -fPIC -DPIC -c /tmp/multimedia/kdetv/plugins/video/v4l/kdetv_v4l.cpp -o ./kdetv/plugins/video/v4l/.libs/kdetv_v4l.o -Wp,-MD,./kdetv/plugins/video/v4l/.deps/kdetv_v4l.TUlo
/usr/X11/include/X11/extensions/Xrandr.h:299: error: expected ',' or '...' before 'delete'
Error creating ./kdetv/plugins/video/v4l/kdetv_v4l.lo. Exit status 1.


Looking in the file, it goes down to this.
int
XRRGetOutputProperty (Display *dpy, RROutput output,
                      Atom property, long offset, long length,
                      Bool delete, Bool pending, Atom req_type,
                      Atom *actual_type, int *actual_format,
                      unsigned long *nitems, unsigned long *bytes_after,
                      unsigned char **prop);



the Bool delete is the problem... Delete is a special word. If I change the "Bool delete" to "Bool delete2", it fixes the problem. It seems like it could be fixed easily in git.
Comment 1 Alan Coopersmith 2007-02-20 13:18:16 UTC

*** This bug has been marked as a duplicate of bug 10046 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.