Modify

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#6670 closed Bugs (fixed)

Apple clang++ -stdc=c++0x breaks on lexical_cast.hpp

Reported by: Arne Schwabe <arne-boost@…> Owned by: apolukhin
Milestone: To Be Determined Component: lexical_cast
Version: Boost 1.49.0 Severity: Problem
Keywords: clang, macos Cc:

Description

clang++ -v
Apple clang version 3.0 (tags/Apple/clang-211.12) (based on LLVM 3.0svn)
Target: x86_64-apple-darwin11.3.0
Thread model: posix

test.cpp:

#include <boost/lexical_cast.hpp>
[12:07]{1}arne@pluto:~/tmp/tmp% clang++ -std=c++0x -I/opt/local/include  test.cpp
In file included from test.cpp:1:
/opt/local/include/boost/lexical_cast.hpp:495:13: error: use of undeclared identifier 'u'
            BOOST_STATIC_CONSTANT(char16_t, zero  = u'0');

[...]

Attachments (0)

Change History (6)

comment:1 Changed 5 years ago by chinux@…

I also have the exact the problem when upgrading to boost 1.49.0

comment:2 Changed 5 years ago by anonymous

  • Component changed from None to lexical_cast
  • Owner set to apolukhin

comment:3 Changed 5 years ago by apolukhin

  • Resolution set to fixed
  • Status changed from new to closed

(In [77691]) Fixes #6670 (now using BOOST_NO_UNICODE_LITERALS macro)

comment:4 Changed 5 years ago by apolukhin

(In [77721]) More workarounds for fixed #6670 (disable basic char16_t and char32_t tests for some compilers, disable optimizations for them)

comment:5 Changed 5 years ago by apolukhin

(In [77745]) More workarounds for fixed #6670 (disable more char16_t and char32_t tests for some compilers)

comment:6 Changed 5 years ago by apolukhin

(In [77804]) Merge lexical_cast from trunk:

  • fixed #6717 (now lexical_cast won`t try to support non confirming swprintf)
  • fixed #6670 (now using BOOST_NO_UNICODE_LITERALS macro to detect unicode literals support)
  • rewritten Jamfile

Add Comment

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain apolukhin.
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.