diff options
| author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-11-14 22:33:41 -0600 |
|---|---|---|
| committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2011-11-14 22:33:41 -0600 |
| commit | 0f92dd542b65bc910caaf190b7c623aa5158c86a (patch) | |
| tree | 120ab7e08fa0ffc354ef58d100f79a33c92aa6e6 /doc/man/man3/qsocket.3qt | |
| parent | d796c9dd933ab96ec83b9a634feedd5d32e1ba3f (diff) | |
| download | tqt3-0f92dd542b65bc910caaf190b7c623aa5158c86a.tar.gz tqt3-0f92dd542b65bc910caaf190b7c623aa5158c86a.zip | |
Fix native TQt3 accidental conversion to tquit
Diffstat (limited to 'doc/man/man3/qsocket.3qt')
| -rw-r--r-- | doc/man/man3/qsocket.3qt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/man/man3/qsocket.3qt b/doc/man/man3/qsocket.3qt index 7dd6273bd..650721783 100644 --- a/doc/man/man3/qsocket.3qt +++ b/doc/man/man3/qsocket.3qt @@ -165,7 +165,7 @@ The signals error(), connected(), readyRead() and connectionClosed() inform you .PP There are several access functions for the socket: state() returns whether the object is idle, is doing a DNS lookup, is connecting, has an operational connection, etc. address() and port() return the IP address and port used for the connection. The peerAddress() and peerPort() functions return the IP address and port used by the peer, and peerName() returns the name of the peer (normally the name that was passed to connectToHost()). socketDevice() returns a pointer to the QSocketDevice used for this socket. .PP -QSocket inherits QIODevice, and reimplements some functions. In general, you can treat it as a QIODevice for writing, and mostly also for reading. The match isn't perfect, since the QIODevice API is designed for devices that are controlled by the same machine, and an asynchronous peer-to-peer network connection isn't tquite like that. For example, there is nothing that matches QIODevice::size() exactly. The documentation for open(), close(), flush(), size(), at(), atEnd(), readBlock(), writeBlock(), getch(), putch(), ungetch() and readLine() describes the differences in detail. +QSocket inherits QIODevice, and reimplements some functions. In general, you can treat it as a QIODevice for writing, and mostly also for reading. The match isn't perfect, since the QIODevice API is designed for devices that are controlled by the same machine, and an asynchronous peer-to-peer network connection isn't quite like that. For example, there is nothing that matches QIODevice::size() exactly. The documentation for open(), close(), flush(), size(), at(), atEnd(), readBlock(), writeBlock(), getch(), putch(), ungetch() and readLine() describes the differences in detail. .PP \fBWarning:\fR QSocket is not suitable for use in threads. If you need to uses sockets in threads use the lower-level QSocketDevice class. .PP |