Re: [boost] Re: Boost.Threads problem

From: Synge Todo (wistaria_at_[hidden])
Date: 2004-07-14 06:10:15

The following line in in boost/thread/detail/lock.hpp (line 66), which
was just changed yesterday, causes a syntax error on Tru64 unix (cxx).

   typedef typename Mutex mutex_type;

(similar lines also in scoped_try_lock and scoped_timed_lock).
AFAIK, we don't need "typename" in this case.  Was this inserted as a
workaround for a broken compiler???  (Or, Tru64 cxx is broken???)

Synge

From: Michael Glassford <glassfordm_at_[hidden]>
Date: Tue, 13 Jul 2004 11:13:30 -0400
> Joel de Guzman wrote:
> 
> > Joel de Guzman wrote:
> > 
> >> Joel de Guzman wrote:
> >>
> >> g++3.2 on MinGW has some trouble compiling
> >> boost/thread/detail/lock.hpp:
> >>
> >> ../../../boost/thread/detail/lock.hpp:30: semicolon missing
> >> after enum declaration
> >>
> > [...]
> > 
> > The same problem is found in thread/read_write_mutex.hpp:37:
> > and thread/detail/read_write_lock.hpp.
> 
> Fixed.
> 
> > *** There are also no newlines at the end of these files. ***
> 
> Fixed.
> 
> > Fixing all those above, Spirit compiles now with only one
> > test failing. The failure is again because of boost.threads
> > (again on MinGW, g++3.2) :
> > 
> > read_write_mutex.cpp: In member function `void
> >    boost::detail::thread::read_write_mutex_impl<Mutex>::do_read_lock()':
> > read_write_mutex.cpp:87: parse error before `('
> >    token
> > 
> > read_write_mutex.cpp: In member function `bool
> >    
> > boost::detail::thread::read_write_mutex_impl<Mutex>::do_try_read_lock()':
> > read_write_mutex.cpp:161: parse error before `('
> >    token
> > 
> > read_write_mutex.cpp: In member function `void
> >    boost::detail::thread::read_write_mutex_impl<Mutex>::do_read_lock() 
> > [with
> >    Mutex = boost::mutex]':
> > 
> > read_write_mutex.cpp:621:   instantiated from here
> > 
> > read_write_mutex.cpp:98: `l' undeclared (first use
> >    this function)
> > 
> > read_write_mutex.cpp:98: (Each undeclared
> >    identifier is reported only once for each function it appears in.)
> > 
> > Any hints?
> 
> No ideas at the moment.
> 
> Mike
> 
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost