summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorJohnny Willemsen <jwillemsen@remedy.nl>2004-06-16 12:23:50 +0000
committerJohnny Willemsen <jwillemsen@remedy.nl>2004-06-16 12:23:50 +0000
commit510d06920b185db9ae8ae639161d4e92a13dce8d (patch)
tree75a390453033b58301b3cccc7415845de2de1b04 /docs
parent2bd668c3afca40e58760343dbdb1ca03970a6b42 (diff)
downloadATCD-510d06920b185db9ae8ae639161d4e92a13dce8d.tar.gz
ChangeLogTag: Wed Jun 16 12:22:31 UTC 2004 Johnny Willemsen <jwillemsen@remedy.nl>
Diffstat (limited to 'docs')
-rw-r--r--docs/ACE-bug-process.html8
-rw-r--r--docs/ACE-development-process.html7
-rw-r--r--docs/ACE-porting.html12
3 files changed, 13 insertions, 14 deletions
diff --git a/docs/ACE-bug-process.html b/docs/ACE-bug-process.html
index f1ed007750a..b9f276657bc 100644
--- a/docs/ACE-bug-process.html
+++ b/docs/ACE-bug-process.html
@@ -70,7 +70,8 @@ affects our work or the work of our sponsors. If you'd like an
immediate response, please contact <A
HREF="mailto:schmidt@cs.wustl.edu">me</A> about becoming a sponsor or
contact one of the companies that provides <A
-HREF="commercial-support.html">commercial support</A> for ACE+TAO. <P>
+HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">
+commercial support</A> for ACE+TAO. <P>
We encourage bug reports for those without support to be posted
initially to the <A
@@ -100,8 +101,7 @@ can not guarantee responses to all postings. <P>
<LI> If it is visible and you haven't received a reply this probably means
that either no one knows the answer or no one has time to answer it.
As always, if you need more predictable help please contact one of
- <A HREF="
- http://www.cs.wustl.edu/~schmidt/commercial-support.html">commercial support</a> companies for ACE+TAO.<P>
+ <A HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">commercial support</a> companies for ACE+TAO.<P>
</UL>
@@ -120,7 +120,7 @@ first check out the TAO <A HREf="http://www.theaceorb.com/faq/">online
FAQ</A> to see if your question has already been answered. If you
require consulting support for ACE and/or TAO, please contact one of
the companies that provides <A
-HREF="commercial-support.html">commercial support</A> for ACE+TAO.<P>
+HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">commercial support</A> for ACE+TAO.<P>
</UL>
diff --git a/docs/ACE-development-process.html b/docs/ACE-development-process.html
index cd4a04858f4..2a6ba473820 100644
--- a/docs/ACE-development-process.html
+++ b/docs/ACE-development-process.html
@@ -151,10 +151,9 @@ will they necessarily pass all of the tests on all platforms. They
will, however, compile cleanly and pass most tests on most platforms.
As usual, we endeavor to fix any problems that arise as quickly as
possible. Naturally, if you require 100% predictable stability and
-support, please contact <A HREF="http://www.theaceorb.com/">OCI</A>
-for TAO commercial support or <A
-HREF="http://www.riverace.com/">Riverace</A> for ACE commercial
-support. <P>
+support, please contact one of the companies that provides <A
+HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">
+commercial support</A> for ACE+TAO.<P>
The first beta following a major/minor release is called a
<EM>bug-fix-only</EM> (BFO) beta. As the name implies this beta will
diff --git a/docs/ACE-porting.html b/docs/ACE-porting.html
index 690b0b2081e..4057fba848a 100644
--- a/docs/ACE-porting.html
+++ b/docs/ACE-porting.html
@@ -44,16 +44,16 @@ we plan to <A HREF="http://www.cs.wustl.edu/~othman/aceconf">auto
configure</A> these files. <P>
<hr align=left width="50%"><P>
-<H4>Port the <CODE>ACE_OS</CODE> Class</H4>
+<H4>Port the <CODE>ACE_OS</CODE> Namespace</H4>
-The <CODE>ACE_OS</CODE> class encapsulates most of variation between
+The <CODE>ACE_OS</CODE> namespace encapsulates most of variation between
the different OS implementations, <EM>e.g.</EM>, UNIX, Win32, and
-various real-time operating systems. It is the core class of the ACE
+various real-time operating systems. It is the core of the ACE
OS abstraction layer. Most work required to port ACE to a new OS
-platform resides in this class. There are <EM>many</EM> examples of
+platform resides in this namespace. There are <EM>many</EM> examples of
how ACE has been ported to other operating systems in the
<CODE>ACE_OS</CODE> class in the
-<CODE>$ACE_ROOT/ace/OS.{h,i,cpp}</CODE> files. <P>
+<CODE>$ACE_ROOT/ace/OS_NS_*.{h,inl,cpp}</CODE> files. <P>
Optional features in pthreads are covered by <CODE>ACE_HAS_*</CODE>
and/or <CODE>ACE_LACKS_*</CODE> macros, which are described in the <A
@@ -86,7 +86,7 @@ you must port the <CODE>ACE_OS::thr_*</CODE> functions. <P>
<hr align=left width="50%"><P>
<H4>Port the C++ Wrapper Components</H4>
-After porting the <CODE>ACE_OS</CODE> class, the next step is to port
+After porting the <CODE>ACE_OS</CODE> namespace, the next step is to port
all of the ACE C++ wrapper components, such as sockets, threads,
synchronization mechanisms. A full list of the categories and classes
can be found in the <A