diff options
Diffstat (limited to 'kdbg/doc/en/types.html')
| -rw-r--r-- | kdbg/doc/en/types.html | 44 |
1 files changed, 22 insertions, 22 deletions
diff --git a/kdbg/doc/en/types.html b/kdbg/doc/en/types.html index 10587b9..8d57799 100644 --- a/kdbg/doc/en/types.html +++ b/kdbg/doc/en/types.html @@ -56,7 +56,7 @@ Sometimes the order in which the names are listed is important <tt>ShlibRE</tt>. KDbg uses this entry to determine if the type table applies to the program being debugged. For this purpose KDbg determines the shared libraries to which the program is linked. If any of the libraries matches -this entry, the type table applies. The regular expression is a Qt-regular +this entry, the type table applies. The regular expression is a TQt-regular expression (the metacharacters <tt>.*?[]^$\</tt> are recognized in the usual way, but there is no possibility to group characters.)</li> @@ -71,9 +71,9 @@ type tables are listed to identify this type table. library is used. Currently, two builtins are supported: <ul> <li> -<tt>QString::Data</tt> is used to display unicode strings of Qt's <tt>QString</tt> +<tt>TQString::Data</tt> is used to display unicode strings of TQt's <tt>TQString</tt> class. See below.</li> -<li><tt>QCharIsShort</tt> is used only in connection with <tt>QString::Data</tt> +<li><tt>TQCharIsShort</tt> is used only in connection with <tt>TQString::Data</tt> to specify that a unicode character is stored in an object of type <tt>short</tt>. See <tt>qt3.kdbgtt</tt> for examples.</li></ul></li> </ul> @@ -125,11 +125,11 @@ this type in the <tt>Types</tt><i>x</i> entries in the <tt>Type Table</tt>.</li> <p><font size=-1>Currently the number of expressions per type is limited to 5. This can easily be changed if it's too restrictive, but I recommend not to go to that limit at all - it will slow down the debugging process.</font></p> -<p>KDbg recognizes a special extension that is used to display Qt 2.x's and Qt 3.x's -unicode strings: If an <tt>Expr</tt><i>x</i> is prepended with <tt>/QString::Data</tt>, -it is assumed that the result of the expression is a pointer to a <tt>QString::Data</tt>. -The value displayed is the unicode string that this instance of <tt>QString::Data</tt> -represents (which can be <tt>QString::null</tt> if it is Qt's well-defined +<p>KDbg recognizes a special extension that is used to display TQt 2.x's and TQt 3.x's +unicode strings: If an <tt>Expr</tt><i>x</i> is prepended with <tt>/TQString::Data</tt>, +it is assumed that the result of the expression is a pointer to a <tt>TQString::Data</tt>. +The value displayed is the unicode string that this instance of <tt>TQString::Data</tt> +represents (which can be <tt>TQString::null</tt> if it is TQt's well-defined null string or <tt>(null)</tt> if the <tt>unicode</tt> member is the null pointer). See <tt>qt2.kdbgtt</tt> for examples.</p> <p>Tip: It is not necessary to define derived types if they ought to be @@ -140,29 +140,29 @@ entry to quickly specify that a type should be treated like a non-leftmost base class for a multiple-inheritance class.</p> <h2> An example</h2> -<p>The example shows how <tt>QString</tt> and <tt>QRect</tt> are defined -in <tt>qt3.kdbgtt</tt>. Furthermore, the template type <tt>QValueVector</tt> -is defined. This example applies to Qt 3.x, which is located in shared library -whose name ends in <tt>libqt-mt.so.3</tt>.</p> +<p>The example shows how <tt>TQString</tt> and <tt>TQRect</tt> are defined +in <tt>qt3.kdbgtt</tt>. Furthermore, the template type <tt>TQValueVector</tt> +is defined. This example applies to TQt 3.x, which is located in shared library +whose name ends in <tt>libtqt-mt.so.3</tt>.</p> <pre>[Type Table] -Types1=QString,QRect -Types2=QValueVector +Types1=TQString,TQRect +Types2=TQValueVector LibDisplayName=libqt 3.x -ShlibRE=libqt-mt\.so\.3$ -EnableBuiltin=QString::Data,QCharIsShort +ShlibRE=libtqt-mt\.so\.3$ +EnableBuiltin=TQString::Data,TQCharIsShort -[QString] +[TQString] Display={ % } -Expr1=/QString::Data (%s).d +Expr1=/TQString::Data (%s).d -[QValueVector] -Template=QValueVector<*> +[TQValueVector] +Template=TQValueVector<*> Display={ size=% shared=% capacity=% } Expr1=($tmp=(%s).sh)->finish-$tmp->start Expr2=(%s).sh->count Expr3=($tmp=(%s).sh)->end-$tmp->start -[QRect] +[TQRect] Display={ tl=(%,%) br=(%,%) } Expr1=(%s).x1 Expr2=(%s).y1 @@ -170,7 +170,7 @@ Expr3=(%s).x2 Expr4=(%s).y2</pre> <p>This example shows these features:</p> <ul> -<li>The name of the template type, <tt>QValueVector</tt> is irrelevant. +<li>The name of the template type, <tt>TQValueVector</tt> is irrelevant. The exact type name is specified under the <tt>Template=</tt> entry. It specifies a single wildcard so that it applies to all specializations. </li> |