diff options
| author | Chris Lattner <sabre@nondot.org> | 2001-10-01 13:18:35 +0000 |
|---|---|---|
| committer | Chris Lattner <sabre@nondot.org> | 2001-10-01 13:18:35 +0000 |
| commit | a9a090b483d1909638417e89a3015c685540618f (patch) | |
| tree | b6f8ca13d6ab81c3488f3915b1f7d1b6e797ce9b /docs | |
| parent | 39f501ca4176bf8ad718fd28b0850887cba3bb31 (diff) | |
| download | llvm-a9a090b483d1909638417e89a3015c685540618f.tar.gz llvm-a9a090b483d1909638417e89a3015c685540618f.tar.bz2 llvm-a9a090b483d1909638417e89a3015c685540618f.tar.xz | |
Comment out a paragraph that refers to a file that no longer exists
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@689 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/CodingStandards.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/CodingStandards.html b/docs/CodingStandards.html index 176f796cf4..489e47694c 100644 --- a/docs/CodingStandards.html +++ b/docs/CodingStandards.html @@ -220,9 +220,9 @@ In practice, this means that you shouldn't assume much about the host compiler, C++ doesn't do too well in the modularity department. There is no real encapsulation or data hiding (unless you use expensive protocol classes), but it is what we have to work with. When you write a public header file (in the LLVM source tree, they live in the top level "include" directory), you are defining a module of functionality.<p> -Modules should be completely independent of each other, except for their dependence. A module is not just a class, a function, or a namespace: <a href="http://www.cuj.com/articles/2000/0002/0002c/0002c.htm">it's a collection of these</a> that defines an interface. This interface may be several functions, classes or data structures, but the important issues is how they work together.<p> +Modules should be completely independent of each other, except for their dependence. A module is not just a class, a function, or a namespace: <a href="http://www.cuj.com/articles/2000/0002/0002c/0002c.htm">it's a collection of these</a> that defines an interface. This interface may be several functions, classes or data structures, but the important issue is how they work together.<p> -One example of this is the <tt>llvm/include/llvm/CFG.h</tt> file. It defines a collection of global functions, template classes, and member functions that are syntactically unrelated to each other. Semantically, however, they all provide useful functionality for operating on a CFG, and so they are bound together.<p> +<!--One example of this is the <tt>llvm/include/llvm/CFG.h</tt> file. It defines a collection of global functions, template classes, and member functions that are syntactically unrelated to each other. Semantically, however, they all provide useful functionality for operating on a CFG, and so they are bound together.<p> --> In general, a module should be implemented with one or more <tt>.cpp</tt> files. Each of these <tt>.cpp</tt> files should include the header that defines their interface first. This ensure that all of the dependences of the module header have been properly added to the module header itself, and are not implicit. System headers should be included after user headers for a translation unit.<p> @@ -646,7 +646,7 @@ If you get some free time, and you haven't read them: do so, you might learn som <address><a href="mailto:sabre@nondot.org">Chris Lattner</a></address> <!-- Created: Tue Jan 23 15:19:28 CST 2001 --> <!-- hhmts start --> -Last modified: Mon Jul 23 15:40:22 CDT 2001 +Last modified: Mon Oct 1 08:17:21 CDT 2001 <!-- hhmts end --> </font> </body></html> |