From e02e31c8b9d854cd62cbe9799228f6e08e882773 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Mon, 5 Dec 2011 22:04:08 -0600 Subject: Sync with latest script --- doc/html/qguardedptr.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/html/qguardedptr.html') diff --git a/doc/html/qguardedptr.html b/doc/html/qguardedptr.html index b62e95867..4b5ebed3e 100644 --- a/doc/html/qguardedptr.html +++ b/doc/html/qguardedptr.html @@ -93,7 +93,7 @@ them using either the *x or the x->member notation.

A guarded pointer will automatically cast to an X*, so you can freely mix guarded and unguarded pointers. This means that if you have a TQGuardedPtr, you can pass it to a function that -retquires a TQWidget*. For this reason, it is of little value to +requires a TQWidget*. For this reason, it is of little value to declare functions to take a TQGuardedPtr as a parameter; just use normal pointers. Use a TQGuardedPtr when you are storing a pointer over time. @@ -139,7 +139,7 @@ there is no referenced object; otherwise returns FALSE.

Cast operator; implements pointer semantics. Because of this function you can pass a TQGuardedPtr<X> to a function where an X* -is retquired. +is required.

bool TQGuardedPtr::operator!= ( const TQGuardedPtr<T> & p ) const

-- cgit v1.2.1