byzhang / rapidjson

Automatically exported from code.google.com/p/rapidjson
MIT License
0 stars 0 forks source link

document.h fails to compile with clang compiler #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Build rapidjson toturial.cpp using any clang tool chain. I used Apple Xcode 
4.2.

What is the expected output? What do you see instead?
The file compiles and builds successfully.

What version of the product are you using? On what operating system?
0.1 with Apple XCode 4.2 on OS X 10.6. But this is independent of OS.

Please provide any additional information below.
clang errors with the following:

/Users/stephenchu/Dropbox/Mac 
Client/Client/../rapidjson/include/rapidjson/document.h:706:4: error: use of 
undeclared identifier 'RawAssign' [3]
                         RawAssign(*stack_.template Pop<ValueType>(1));
                         ^

This is a know issue with clang. The issue and solution can be found here: 
http://blog.llvm.org/2009/12/dreaded-two-phase-name-lookup.html

Adding qualifier this to the call fixes the problem:

            this->RawAssign(*stack_.template Pop<ValueType>(1));

Original issue reported on code.google.com by stephe...@gmail.com on 10 Feb 2012 at 6:47

GoogleCodeExporter commented 9 years ago

Original comment by milo...@gmail.com on 11 Feb 2012 at 1:22

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r55.

Original comment by milo...@gmail.com on 19 Feb 2012 at 2:53

GoogleCodeExporter commented 9 years ago
Issue 29 has been merged into this issue.

Original comment by milo...@gmail.com on 13 Nov 2012 at 9:42

GoogleCodeExporter commented 9 years ago
Issue 42 has been merged into this issue.

Original comment by milo...@gmail.com on 14 Nov 2012 at 3:38

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
This is not fixed,  Issue 42  and Issue 73 show an additional error that is 
still present.

Issue 73 has a patch.

Original comment by jonathan...@gmail.com on 18 Jun 2013 at 9:17