search for: mypair

...nforming implementation (as does dinkumware too I think...). In comparison (since you mentioned horrible interfaces), how about something simple like returning a float followed by a pipe followed by an integer list separated by commas and parsing it into a std::pair<float,vector<int> > myPair; Also, I might be wrong on some of the regex syntax, it has been a *long* time since I ever touched regex inside a program (ever since I started using boost::spirit, only use it for grep and its kin anymore), but it should get the idea across. I use this regex for each of the things below: std:...

On Aug 23, 2009, at 5:50 PM, OvermindDL1 wrote: > On Sun, Aug 23, 2009 at 6:32 PM, Daniel Dunbar<daniel at zuster.org> > wrote: >> This is too heavy, and we don't need the extra features, and regexec >> is well tested and much more standard. Unless there is an >> overwhelming > > 'regexec' I had never heard of, figured it was a library, turns

...e Visual Studio 2010 > C++ > > Compiler and not really related to clang/llvm. The following snippet of > code > > does NOT compile in 2010.. > > > > #include <vector> > > int main(int argc, char* argv[]) > > { > > std::pair<int, void*> mypair(0, NULL); > > return 0; > > } > > > > That's perfectly fine -- it never #includes <utility>, > so there's no reason for std::pair to be in scope. > #include <vector> int main(int argc, char* argv[]) { std::pair<int, void*> mypair(0, (...

...oblem seems to be a much larger issue with the Visual Studio 2010 C++ > Compiler and not really related to clang/llvm. The following snippet of code > does NOT compile in 2010.. > > #include <vector> > int main(int argc, char* argv[]) > { >     std::pair<int, void*> mypair(0, NULL); >     return 0; > } > That's perfectly fine -- it never #includes <utility>, so there's no reason for std::pair to be in scope.

...the loop on my findings. The problem seems to be a much larger issue with the Visual Studio 2010 C++ Compiler and not really related to clang/llvm. The following snippet of code does *NOT *compile in 2010.. #include <vector> int main(int argc, char* argv[]) { std::pair<int, void*> mypair(0, NULL); return 0; } Tom. On Sat, May 1, 2010 at 8:57 PM, Tom van Dijck <llvm at tomvandijck.com> wrote: > Hey, > > So I tried to fix these errors, and have everything compiling now... not > too difficult, just annoying. > > error C2248: 'llvm::EquivalenceClass...

...t;> > Compiler and not really related to clang/llvm. The following snippet of >> code >> > does NOT compile in 2010.. >> > >> > #include <vector> >> > int main(int argc, char* argv[]) >> > { >> > std::pair<int, void*> mypair(0, NULL); >> > return 0; >> > } >> > >> >> That's perfectly fine -- it never #includes <utility>, >> so there's no reason for std::pair to be in scope. >> > > #include <vector> > int main(int argc, char* argv[]) &gt...

Hey, So I tried to fix these errors, and have everything compiling now... not too difficult, just annoying. error C2248: 'llvm::EquivalenceClasses< > > ElemTy>::ECValue::ECValue' : cannot access private member declared in class > 'llvm::EquivalenceClasses<ElemTy>::ECValue' C:\Program Files > (x86)\Microsoft Visual Studio 10.0\VC\include\xmemory 208

Hey, Downloaded the release, used CMake to create solution... building mostly seems to be OK, except for a couple of compiler errors. warning C4090: 'function' : different 'const' qualifiers d:\companyone\external\llvm\source\llvm-2.7\lib\support\regengine.inc 188 error C2248: 'llvm::EquivalenceClasses<ElemTy>::ECValue::ECValue' : cannot access private member