libX11: fixing public headers?
tilman at code-monkey.de
Sun Apr 1 02:50:59 PDT 2007
I recently filed and fixed this bug against libX11:
libX11 mixes up char* vs const char* in a lot of places.
Some of these errors affect the public header Xlib.h, too (it's the
first two chunks of the diff). I changed char* to const char* in two
What does everyone think about adding "const" there?
Can/should we do that?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Q: What is the most annoying thing on usenet and in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the xorg