bug report: boost::tokenizer with VC6

The boost release 1.28.0 of the tokenizer library has the following problem: There are 5 examples, namely, simple_example_1.cpp thru simple_example_5.cpp If I change the main() in each of the 5 to to main1() thru main5() and return 0; the vc60 compiler generates an internal compiler error when parsing the file boost\iterator_adapters.hpp on line 869, where it is parsing the following lines: reference operator*() const { return policies().dereference(*this); }

The boost release 1.28.0 of the tokenizer library has the following
"Navi Singh" <yg-boost-users@m.gmane.org> wrote in message news:aeatsq$fqe$1@main.gmane.org... problem:
There are 5 examples, namely, simple_example_1.cpp thru
simple_example_5.cpp
If I change the main() in each of the 5 to to main1() thru main5() and return 0; the vc60 compiler generates an internal compiler error
Why do you think this is a problem with the Boost library?

The following message was posted last year, but I think I ran across a similar or related bug today: Using MSVC6 and Boost 1.29.0, if you #include <boost/tokenizer.hpp> in your precompiled headers, the following line crashes the compiler identically to the message below: boost::tokenizer<>::iterator it; Simply moving the #include out of the precompiled header avoids the crash. If there is a better workaround or fix I would love to hear it. Thanks, Ben --- In Boost-Users@yahoogroups.com, "Navi Singh" <yg-boost-users@m...> wrote:
The boost release 1.28.0 of the tokenizer library has the following problem: There are 5 examples, namely, simple_example_1.cpp thru simple_example_5.cpp. If I change the main() in each of the 5 to to main1() thru main5() and return 0; the vc60 compiler generates an internal compiler error when parsing the file boost\iterator_adapters.hpp on line 869, where it is parsing the following lines: reference operator*() const { return policies().dereference(*this); }
participants (3)
-
David Abrahams
-
Navi Singh
-
totalnubee <totalnubee@dslextreme.com>