Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Use @import rather than @__experimental_modules_import, since the | Douglas Gregor | 2012-12-11 | 1 | -1/+1 |
| | | | | | | latter is rather a mess to type. llvm-svn: 169919 | ||||
* | Change @import to @__experimental_modules_import. We are not ready to ↵ | Ted Kremenek | 2012-03-01 | 1 | -1/+1 |
| | | | | | | | | commit to a particular syntax for modules, and don't have time to push it forward in the near future. llvm-svn: 151841 | ||||
* | Eliminate the uglified keyword __import_module__ for importing | Douglas Gregor | 2012-01-03 | 1 | -1/+1 |
| | | | | | | | | | | | | | modules. This leaves us without an explicit syntax for importing modules in C/C++, because such a syntax needs to be discussed first. In Objective-C/Objective-C++, the @import syntax is used to import modules. Note that, under -fmodules, C/C++ programs can import modules via the #include mechanism when a module map is in place for that header. This allows us to work with modules in C/C++ without committing to a syntax. llvm-svn: 147467 | ||||
* | Add test case for mutually recursive modules | Douglas Gregor | 2011-09-15 | 1 | -0/+3 |
llvm-svn: 139838 |