From: Sohail Somani (s.somani_at_[hidden])
Date: 2007-01-02 17:47:19
Any takers? The workaround I've found for the problem below is to
#define _MSC_EXTENSIONS before including any boost thread headers. It
/appears/ that this is only necessary when separately compiling boost
threads. Sorry for the cross-post.
> With Visual C++, I can't seem to determine why if I simply include
> boost/threads/once.hpp, I need to enable language extensions for that
> translation unit. I'm going to dig into this further today but I would
> appreciate if someone has figured out a solution short of allowing
> language extensions. I can understand requiring it for building boost
> threads (as windows.h seems to have some extended syntax) but I'm not
> sure of the logic behind requiring client code to use it as well.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk