Hi,
I've just solved a problem with a method called check() on Mac OSX. It was
quite a head scratcher, so I thought I'd throw some light on it so others are
aware.
Mac OSX defines an assert header called check() so I was getting error like:
Stephen Kelly spaketh:
http://boost.2283326.n4.nabble.com/Boost-with-Darwin-Mac-gcc-4-0-1-
td2580330.html
So, keep in mind - for portability treat 'check' as an out of bounds name
for a method or variable.
Thiago Macieira respondeth:
Also to avoid:
sun
m_volume
On Monday, 9 de January de 2012 14.46.54, =?ISO-8859-1?Q?Gábor?= Lehel
wrote:
Yet more:
- major
- minor
These are defined to gnu_dev_major and gnu_dev_minor, I'm not quite
sure by what (GCC? glibc?).
/usr/include/sys/sysmacros.h:# define major(dev) gnu_dev_major (dev)
$ grep
2012/1/9 Gábor Lehel illiss...@gmail.com:
Perhaps we could use GCC's poison pragma[1] to make sure that no one
uses them? In some cases it would just be replacing one error message
with another (though perhaps a more user-friendly one), but in other
cases it would substitute an error for no
2012/1/9 Stephen Kelly stephen.ke...@kdab.com:
On Monday, January 09, 2012 18:00:29 Gábor Lehel wrote:
2012/1/9 Gábor Lehel illiss...@gmail.com:
Perhaps we could use GCC's poison pragma[1] to make sure that no one
uses them? In some cases it would just be replacing one error message
2012/1/9 Gábor Lehel illiss...@gmail.com:
2012/1/9 Stephen Kelly stephen.ke...@kdab.com:
On Monday, January 09, 2012 18:00:29 Gábor Lehel wrote:
2012/1/9 Gábor Lehel illiss...@gmail.com:
Perhaps we could use GCC's poison pragma[1] to make sure that no one
uses them? In some cases it
