activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tab...@apache.org
Subject svn commit: r924487 - /activemq/activemq-cpp/trunk/activemq-cpp/src/main/decaf/lang/Thread.h
Date Wed, 17 Mar 2010 20:56:09 GMT
Author: tabish
Date: Wed Mar 17 20:56:09 2010
New Revision: 924487

URL: http://svn.apache.org/viewvc?rev=924487&view=rev
Log:
Cleanup the API docs to fix Doxygen warnings.

Modified:
    activemq/activemq-cpp/trunk/activemq-cpp/src/main/decaf/lang/Thread.h

Modified: activemq/activemq-cpp/trunk/activemq-cpp/src/main/decaf/lang/Thread.h
URL: http://svn.apache.org/viewvc/activemq/activemq-cpp/trunk/activemq-cpp/src/main/decaf/lang/Thread.h?rev=924487&r1=924486&r2=924487&view=diff
==============================================================================
--- activemq/activemq-cpp/trunk/activemq-cpp/src/main/decaf/lang/Thread.h (original)
+++ activemq/activemq-cpp/trunk/activemq-cpp/src/main/decaf/lang/Thread.h Wed Mar 17 20:56:09
2010
@@ -39,24 +39,24 @@ namespace lang{
     class ThreadProperties;
 
     /**
-     * A {@code Thread} is a concurrent unit of execution. It has its own call stack for
+     * A Thread is a concurrent unit of execution. It has its own call stack for
      * methods being invoked, their arguments and local variables. Each process has at
-     * least one main {@code Thread} running when it is started; typically, there are
+     * least one main Thread running when it is started; typically, there are
      * several others for housekeeping. The application might decide to launch additional
-     * {@code Thread}s for specific purposes.
+     * Threads for specific purposes.
      *
-     * {@code Thread}s in the same process interact and synchronize by the use of shared
+     * Threads in the same process interact and synchronize by the use of shared
      * objects and monitors associated with these objects.
      *
-     * There are basically two main ways of having a {@code Thread} execute application
-     * code. One is providing a new class that extends {@code Thread} and overriding
-     * its {@link #run()} method. The other is providing a new {@code Thread} instance
+     * There are basically two main ways of having a Thread execute application
+     * code. One is providing a new class that extends Thread and overriding
+     * its {@link #run()} method. The other is providing a new Thread instance
      * with a {@link Runnable} object during its creation. In both cases, the
-     * {@link #start()} method must be called to actually execute the new {@code Thread}.
+     * {@link #start()} method must be called to actually execute the new Thread.
      *
-     * Each {@code Thread} has an integer priority that basically determines the amount
-     * of CPU time the {@code Thread} gets. It can be set using the {@link #setPriority(int)}
-     * method. A {@code Thread} can also be made a daemon, which makes it run in the
+     * Each Thread has an integer priority that basically determines the amount
+     * of CPU time the Thread gets. It can be set using the {@link #setPriority(int)}
+     * method. A Thread can also be made a daemon, which makes it run in the
      * background. The latter also affects VM termination behavior: the VM does not
      * terminate automatically as long as there are non-daemon threads running.
      *



Mime
View raw message