7 May
2009
7 May
'09
7:53 p.m.
Michael Caisse wrote:
I'm not certain if this is an asio issue or spirit2 issue (or user error).
This is due to an identifier conflict (on "B0") between a Linux system header (included by asio) and Proto (included by Spirit2). A "#undef B0" between the inclusions of ASIO and Spirit2 should also fix the issue. FYI, Boost 1.39 which no longer exhibits this behavior. HTH, François