From 0ada0fd31a540e4b01a75ca52ae6fbbd37852bb3 Mon Sep 17 00:00:00 2001
From: Beman Dawes
Date: Fri, 22 Sep 2000 18:06:56 +0000
Subject: [PATCH] Minor updates
[SVN r7769]
---
more/feature_model_diagrams.htm | 3 ++-
more/header.htm | 13 ++-----------
more/index.htm | 5 ++++-
more/lib_guide.htm | 27 +++++++++++++++++++++++----
4 files changed, 31 insertions(+), 17 deletions(-)
diff --git a/more/feature_model_diagrams.htm b/more/feature_model_diagrams.htm
index 40e807be3b..2b5cf151ed 100644
--- a/more/feature_model_diagrams.htm
+++ b/more/feature_model_diagrams.htm
@@ -9,6 +9,7 @@
+
Feature Model Diagrams in text and HTML
By Beman Dawes
Introduction
@@ -95,7 +96,7 @@ assuming no constraints.
Krzysztof Czarnecki and Ulrich W. Eisenecker, Generative
Programming, Addison-Wesley, 2000, ISBN 0-210-30977-7
-Revised 23 July 2000
+Revised 25 August 2000
© Copyright Beman Dawes, 2000
diff --git a/more/header.htm b/more/header.htm
index e4d4c269d4..bf0347cb73 100644
--- a/more/header.htm
+++ b/more/header.htm
@@ -28,15 +28,6 @@ be "good neighbors".
these are also reasonable guidelines for general use.
- Headers should have a .hpp (lowercase) filename extension.
- - Identify the file with an initial comment line. The sample header
- identifies both the name of the header and the library it is a part of.
- - Specify copyright ownership and any restrictions on use. If you
- don't want to retain ownership, say something like "Written by Jane
- Programmer and placed in the public domain".
- - Supply version information, possibly generated automatically by your
- version control system.
- - Macro names should be all uppercase, and begin with the namespace
- name. Underscores separate words.
- Wrap the header in #ifndef guards so that multiple inclusion is
benign. Use a naming convention that minimizes the chance of clashes
with macro names from other's code. The sample
@@ -68,7 +59,7 @@ these are also reasonable guidelines for general use.
// in all copies. This software is provided "as is" without express or implied
// warranty, and with no claim as to its suitability for any purpose.
-// $Id$ or other version information
+// See http://www.boost.org for updates, documentation, and revision history.
#ifndef BOOST_FURBALL_HPP
#define BOOST_FURBALL_HPP
@@ -95,7 +86,7 @@ commenting ending braces, and similar formatting issues. These stylistic
issues are viewed as personal preferences and are not part of the Boost Header
Policy.
-Revised 27 July, 2000
+Revised 06 August, 2000