Modify

Opened 5 years ago

Closed 5 years ago

#6400 closed Bugs (fixed)

gcc3.4.4(cygwin) code will not compile if macro BOOST_LCAST_NO_WCHAR_T is defined

Reported by: grzechu81@… Owned by: nasonov
Milestone: Boost 1.49.0 Component: lexical_cast
Version: Boost 1.48.0 Severity: Showstopper
Keywords: gcc.3.4.4 cygwin BOOST_LCAST_NO_WCHAR_T Cc: antoshkka@…

Description

Using compiler gcc 3.4.4 (cygwin) and boost 1.48.0 following code:

#include <boost/lexical_cast.hpp>
int main(int argc, char * argv[])
{
    return 0;
}

will result in compiler error:

.../boost_1_48_0/boost/lexical_cast.hpp: In function `bool boost::detail::parse_inf_nan_impl(const CharT*, const CharT*, T&, const CharT*, const CharT*, const CharT*, const CharT*, CharT, CharT)':
.../boost_1_48_0/boost/lexical_cast.hpp:651: error: incomplete type `boost::detail::lcast_char_constants<wchar_t>' used in nested name specifier
.../boost_1_48_0/boost/lexical_cast.hpp:652: error: incomplete type `boost::detail::lcast_char_constants<wchar_t>' used in nested name specifier

It is because if using this compiler, macro BOOST_NO_STD_WSTRING is defined , so.. lexical cast defines BOOST_LCAST_NO_WCHAR_T.

Some code is #ifdef'ed with this macro but not all that should. So there is discrepancy.

Attachments (0)

Change History (2)

comment:1 Changed 5 years ago by Grzegorz Wolszczak <grzechu81@…>

  • Summary changed from code will not compile if macro BOOST_LCAST_NO_WCHAR_T is defined to gcc3.4.4(cygwin) code will not compile if macro BOOST_LCAST_NO_WCHAR_T is defined

comment:2 Changed 5 years ago by apolukhin

  • Cc antoshkka@… added
  • Milestone changed from To Be Determined to Boost 1.49.0
  • Resolution set to fixed
  • Status changed from new to closed

Thanks for reporting an issue. It is already fixed in trunk. This bug is a duplicate for #6127

Add Comment

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain nasonov.
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.