Automated update from Qt3

1 files changed, 18 insertions, 18 deletions

diff --git a/doc/man/man3/qsocketdevice.3qt b/doc/man/man3/qsocketdevice.3qt
index 2a922fa1f..aaf0c39c1 100644
--- a/doc/man/man3/qsocketdevice.3qt
+++ b/doc/man/man3/qsocketdevice.3qt
@@ -73,10 +73,10 @@ Inherits QIODevice.
 .BI "virtual void \fBsetSendBufferSize\fR ( uint size )"
 .br
 .ti -1c
-.BI "virtual bool \fBconnect\fR ( const QHostAddress & addr, Q_UINT16 port )"
+.BI "virtual bool \fBconnect\fR ( const QHostAddress & addr, TQ_UINT16 port )"
 .br
 .ti -1c
-.BI "virtual bool \fBbind\fR ( const QHostAddress & address, Q_UINT16 port )"
+.BI "virtual bool \fBbind\fR ( const QHostAddress & address, TQ_UINT16 port )"
 .br
 .ti -1c
 .BI "virtual bool \fBlisten\fR ( int backlog )"
@@ -85,25 +85,25 @@ Inherits QIODevice.
 .BI "virtual int \fBaccept\fR ()"
 .br
 .ti -1c
-.BI "Q_LONG \fBbytesAvailable\fR () const"
+.BI "TQ_LONG \fBbytesAvailable\fR () const"
 .br
 .ti -1c
-.BI "Q_LONG \fBwaitForMore\fR ( int msecs, bool * timeout = 0 ) const"
+.BI "TQ_LONG \fBwaitForMore\fR ( int msecs, bool * timeout = 0 ) const"
 .br
 .ti -1c
-.BI "virtual Q_LONG \fBreadBlock\fR ( char * data, Q_ULONG maxlen )"
+.BI "virtual TQ_LONG \fBreadBlock\fR ( char * data, TQ_ULONG maxlen )"
 .br
 .ti -1c
-.BI "virtual Q_LONG \fBwriteBlock\fR ( const char * data, Q_ULONG len )"
+.BI "virtual TQ_LONG \fBwriteBlock\fR ( const char * data, TQ_ULONG len )"
 .br
 .ti -1c
-.BI "virtual Q_LONG \fBwriteBlock\fR ( const char * data, Q_ULONG len, const QHostAddress & host, Q_UINT16 port )"
+.BI "virtual TQ_LONG \fBwriteBlock\fR ( const char * data, TQ_ULONG len, const QHostAddress & host, TQ_UINT16 port )"
 .br
 .ti -1c
-.BI "Q_UINT16 \fBport\fR () const"
+.BI "TQ_UINT16 \fBport\fR () const"
 .br
 .ti -1c
-.BI "Q_UINT16 \fBpeerPort\fR () const"
+.BI "TQ_UINT16 \fBpeerPort\fR () const"
 .br
 .ti -1c
 .BI "QHostAddress \fBaddress\fR () const"
@@ -217,7 +217,7 @@ Returns the address of this socket device. This may be 0.0.0.0 for a while, but
 Returns TRUE if the address of this socket can be used by other sockets at the same time, and FALSE if this socket claims exclusive ownership.
 .PP
 See also setAddressReusable().
-.SH "bool QSocketDevice::bind ( const QHostAddress & address, Q_UINT16 port )\fC [virtual]\fR"
+.SH "bool QSocketDevice::bind ( const QHostAddress & address, TQ_UINT16 port )\fC [virtual]\fR"
 Assigns a name to an unnamed socket. The name is the host address \fIaddress\fR and the port number \fIport\fR. If the operation succeeds, bind() returns TRUE; otherwise it returns FALSE without changing what port() and address() return.
 .PP
 bind() is used by servers for setting up incoming connections. Call bind() before listen().
@@ -229,11 +229,11 @@ Note that this function does not set error().
 \fBWarning:\fR On Windows, this function always returns TRUE since the ioctlsocket() function is broken.
 .PP
 See also setBlocking() and isValid().
-.SH "Q_LONG QSocketDevice::bytesAvailable () const"
+.SH "TQ_LONG QSocketDevice::bytesAvailable () const"
 Returns the number of bytes available for reading, or -1 if an error occurred.
 .PP
 \fBWarning:\fR On Microsoft Windows, we use the ioctlsocket() function to determine the number of bytes queued on the socket. According to Microsoft (KB Q125486), ioctlsocket() sometimes returns an incorrect number. The only safe way to determine the amount of data on the socket is to read it using readBlock(). QSocket has workarounds to deal with this problem.
-.SH "bool QSocketDevice::connect ( const QHostAddress & addr, Q_UINT16 port )\fC [virtual]\fR"
+.SH "bool QSocketDevice::connect ( const QHostAddress & addr, TQ_UINT16 port )\fC [virtual]\fR"
 Connects to the IP address and port specified by \fIaddr\fR and \fIport\fR. Returns TRUE if it establishes a connection; otherwise returns FALSE. If it returns FALSE, error() explains why.
 .PP
 Note that error() commonly returns NoError for non-blocking sockets; this just means that you can call connect() again in a little while and it'll probably succeed.
@@ -253,11 +253,11 @@ See also bind() and accept().
 Returns the address of the port this socket device is connected to. This may be 0.0.0.0 for a while, but is set to something sensible as soon as a sensible value is available.
 .PP
 Note that for Datagram sockets, this is the source port of the last packet received.
-.SH "Q_UINT16 QSocketDevice::peerPort () const"
+.SH "TQ_UINT16 QSocketDevice::peerPort () const"
 Returns the port number of the port this socket device is connected to. This may be 0 for a while, but is set to something sensible as soon as a sensible value is available.
 .PP
 Note that for Datagram sockets, this is the source port of the last packet received, and that it is in native byte order.
-.SH "Q_UINT16 QSocketDevice::port () const"
+.SH "TQ_UINT16 QSocketDevice::port () const"
 Returns the port number of this socket device. This may be 0 for a while, but is set to something sensible as soon as a sensible value is available.
 .PP
 Note that Qt always uses native byte order, i.e. 67 is 67 in Qt; there is no need to call htons().
@@ -267,7 +267,7 @@ Returns the socket's protocol family, which is one of Unknown, IPv4, or IPv6.
 QSocketDevice either creates a socket with a well known protocol family or it uses an already existing socket. In the first case, this function returns the protocol family it was constructed with. In the second case, it tries to determine the protocol family of the socket; if this fails, it returns Unknown.
 .PP
 See also Protocol and setSocket().
-.SH "Q_LONG QSocketDevice::readBlock ( char * data, Q_ULONG maxlen )\fC [virtual]\fR"
+.SH "TQ_LONG QSocketDevice::readBlock ( char * data, TQ_ULONG maxlen )\fC [virtual]\fR"
 Reads \fImaxlen\fR bytes from the socket into \fIdata\fR and returns the number of bytes read. Returns -1 if an error occurred. Returning 0 is not an error. For Stream sockets, 0 is returned when the remote host closes the connection. For Datagram sockets, 0 is a valid datagram size.
 .PP
 Reimplemented from QIODevice.
@@ -323,7 +323,7 @@ See also isValid() and type().
 Returns the socket type which is either QSocketDevice::Stream or QSocketDevice::Datagram.
 .PP
 See also socket().
-.SH "Q_LONG QSocketDevice::waitForMore ( int msecs, bool * timeout = 0 ) const"
+.SH "TQ_LONG QSocketDevice::waitForMore ( int msecs, bool * timeout = 0 ) const"
 Wait up to \fImsecs\fR milliseconds for more data to be available. If \fImsecs\fR is -1 the call will block indefinitely.
 .PP
 Returns the number of bytes available for reading, or -1 if an error occurred.
@@ -333,13 +333,13 @@ If \fItimeout\fR is non-null and no error occurred (i.e. it does not return -1):
 \fBWarning:\fR This is a blocking call and should be avoided in event driven applications.
 .PP
 See also bytesAvailable().
-.SH "Q_LONG QSocketDevice::writeBlock ( const char * data, Q_ULONG len )\fC [virtual]\fR"
+.SH "TQ_LONG QSocketDevice::writeBlock ( const char * data, TQ_ULONG len )\fC [virtual]\fR"
 Writes \fIlen\fR bytes to the socket from \fIdata\fR and returns the number of bytes written. Returns -1 if an error occurred.
 .PP
 This is used for QSocketDevice::Stream sockets.
 .PP
 Reimplemented from QIODevice.
-.SH "Q_LONG QSocketDevice::writeBlock ( const char * data, Q_ULONG len, const QHostAddress & host, Q_UINT16 port )\fC [virtual]\fR"
+.SH "TQ_LONG QSocketDevice::writeBlock ( const char * data, TQ_ULONG len, const QHostAddress & host, TQ_UINT16 port )\fC [virtual]\fR"
 This is an overloaded member function, provided for convenience. It behaves essentially like the above function.
 .PP
 Writes \fIlen\fR bytes to the socket from \fIdata\fR and returns the number of bytes written. Returns -1 if an error occurred.