summaryrefslogtreecommitdiffstats
path: root/doc/object.doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc/object.doc')
-rw-r--r--doc/object.doc16
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/object.doc b/doc/object.doc
index 50c7a1fd..5282000c 100644
--- a/doc/object.doc
+++ b/doc/object.doc
@@ -72,7 +72,7 @@ Many of these TQt features are implemented with standard C++
techniques, based on inheritance from \l TQObject. Others, like the
object communication mechanism and the dynamic property system,
require the \link metaobjects.html Meta Object System \endlink provided
-by Qt's own \link moc.html Meta Object Compiler (moc) \endlink.
+by TQt's own \link tqmoc.html Meta Object Compiler (tqmoc) \endlink.
The Meta Object System is a C++ extension that makes the language
better suited to true component GUI programming. Although templates can
@@ -646,15 +646,15 @@ beginning, without even having to think about design patterns.
<h3>2. Precompilers are good</h3>
-Qt's <tt>moc</tt> (Meta Object Compiler) provides a clean way to go
+TQt's <tt>tqmoc</tt> (Meta Object Compiler) provides a clean way to go
beyond the compiled language's facilities. It does so by generating
additional C++ code which can be compiled by any standard C++ compiler.
-The <tt>moc</tt> reads C++ source files. If it finds one or more class
+<tt>TQMoc</tt> reads C++ source files. If it finds one or more class
declarations that contain the "TQ_OBJECT" macro, it produces another C++
source file which contains the meta object code for those classes. The
-C++ source file generated by the <tt>moc</tt> must be compiled and
+C++ source file generated by <tt>tqmoc</tt> must be compiled and
linked with the implementation of the class (or it can be
-<tt>#included</tt> into the class's source file). Typically <tt>moc</tt>
+<tt>#included</tt> into the class's source file). Typically <tt>tqmoc</tt>
is not called manually, but automatically by the build system, so it
requires no additional effort by the programmer.
@@ -686,7 +686,7 @@ object model is a clear disadvantage over the dynamic messaging approach
of Objective C when it comes to component-based graphical user interface
programming. What's good for a high end database server or an operating
system isn't necessarily the right design choice for a GUI frontend.
-With <tt>moc</tt>, we have turned this disadvantage into an advantage,
+With <tt>tqmoc</tt>, we have turned this disadvantage into an advantage,
and added the flexibility required to meet the challenge of safe and
efficient graphical user interface programming.
@@ -746,7 +746,7 @@ listener interface rather than signals and slots.
<h3>5. No limits</h3>
-Because we had the <tt>moc</tt> for signals and slots, we could add
+Because we had <tt>tqmoc</tt> for signals and slots, we could add
other useful things to it that could not not be done with templates.
Among these are scoped translations via a generated <tt>tr()</tt>
function, and an advanced property system with introspection and
@@ -755,7 +755,7 @@ advantage: a powerful and generic user interface design tool like Qt
Designer would be a lot harder to write - if not impossible - without a
powerful and introspective property system.
-C++ with the <tt>moc</tt> preprocessor essentially gives us the
+C++ with <tt>tqmoc</tt> preprocessor essentially gives us the
flexibility of Objective-C or of a Java Runtime Environment, while
maintaining C++'s unique performance and scalability advantages. It is
what makes TQt the flexible and comfortable tool we have today.