Coming back to the issues that I had integrating LLVM with
MSSP, will the code in include/Support also be put in the
llvm namespace? That will solve many problems and help prevent
others.
Rahul
Coming back to the issues that I had integrating LLVM with
MSSP, will the code in include/Support also be put in the
llvm namespace? That will solve many problems and help prevent
others.
Rahul
Coming back to the issues that I had integrating LLVM with
MSSP, will the code in include/Support also be put in the
llvm namespace? That will solve many problems and help prevent
others.
Absolutely.
-Chris
Yes, pretty much. There are a few things that will go in the std namespace because its the
way it is and a more natural fit. The other two namespaces already in use (cl and DOT) will
be placed under the llvm namespace. The goal is to get everything that is currently at top
level and put it in llvm. This means that in your programs, you wouldn’t use:
cl::XYZ
anymore but:
llvm::XYZ.
Or, you can use a “using namespace llvm” to retain backwards compatibility.
Reid.
<i>Coming back to the issues that I had integrating LLVM with MSSP, will the code in include/Support also be put in the llvm namespace? That will solve many problems and help prevent others. Rahul >Date: Sun, 9 Nov 2003 10:13:03 -0600 (CST) >From: Chris Lattner <sabre@nondot.org> >Subject: [LLVMdev] LLVM namespac'ification >To: LLVMdev List <llvmdev@cs.uiuc.edu> > > >This is just a heads up: Reid Spencer is working up a changeset for LLVM >which will put all of the LLVM classes into an 'llvm' namespace. This >will make it possible to integrate LLVM with other C++ packages that use >classes like 'Type' and 'User'. > >This should cause very little impact on the actual source base, other than >the 'namespace llvm' in header files, and a 'using namespace llvm' in the >.cpp files. > >If you have questions or concerns, llvmdev is the place for them! :) > >Thanks Reid! > >-Chris > >-- ></i><i>[http://llvm.cs.uiuc.edu/](http://llvm.cs.uiuc.edu/) >[http://www.nondot.org/~sabre/Projects/](http://www.nondot.org/~sabre/Projects/) > > > >_______________________________________________ >LLVM Developers mailing list >LLVMdev@cs.uiuc.edu [http://llvm.cs.uiuc.edu](http://llvm.cs.uiuc.edu) >[http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev](http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev) _______________________________________________ LLVM Developers mailing list LLVMdev@cs.uiuc.edu [http://llvm.cs.uiuc.edu](http://llvm.cs.uiuc.edu) [http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev](http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev)</i>
> <br><br><br><br><br><br> |
> - |
Note that the LLVM sourcebase itself won't use llvm:: - it will use a
'using namespace llvm;' in all .cpp files, to avoid uglification.
-Chris
Chris,
What's the current status of the test suite. After putting everything
in the llvm namespace and getting everything to link, I am getting
only about 75% of the tests passing. Is this to be expected or have
I broken something?
Reid.
You can see the current results of the nightly tests for X86 and Sparc
architectures here:
http://llvm.cs.uiuc.edu/testresults/
However, the nightly tester does not test the "Regressions" directory,
for those QMTest is used, and the expected failures are hard-coded into
the qmtest database, but John Criswell knows more about this than I do.