| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
option "-error". Essentially ignores the option, always
returning an empty string.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* generic/tclIntPlatDecls.h:
* mac/tclMacChan.c:
* mac/tclMacFCmd.c:
* mac/tclMacFile.c:
* mac/tclMacInit.c:
* mac/tclMacLoad.c:
* mac/tclMacResource.c:
* mac/tclMacSock.c: TIP 27 CONSTification induced changes
* tests/event.test:
* tests/main.test: added catches/constraints to test that
use features that don't exist on the mac.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
of TIP 27. Several minor documentation corrections as well.
* Updated channel driver interface according to the guidelines of
TIP 27. See also [Bug 500348].
* Moved Tcl_EolTranslation enum declaration from generic/tcl.h to
generic/tclInt.h (renamed to TclEolTranslation). It is not used
anywhere in Tcl's public interface.
|
| |
|
|
|
|
| |
** changes for 8.4, some already backported to 8.3.4 (patch #435658)
see ChangeLog for details
|
| | |
|
| |
|
|
| |
some error handling marginally better for Mac sockets. It is
still somewhat flakey, however.
* mac/tclMacSock.c (TcpClose): Add timeouts to the close - these don't seem to
be honored, however.
* Use a separate PB for the release, since an async connect socket will still
be using the original buffer.
* Make sure TCPRelease returns noErr before freeing the recvBuff. If the call
returns an error, then the buffer is not right.
* mac/tclMacSocket.c (CreateSocket): Add timeouts to the async create. These
don't seem to trigger, however. Sigh...
* mac/tclMacSocket.c (WaitForSocketEvent): If an TCP_ASYNC_CONNECT socket errors
out, then return EWOULDBLOCK & error out.
* mac/tclMacSock.c: (NotifyRoutine) Added a NotifyRoutine for experimenting
with MacTCP.
|
| |
|
|
| |
benign to just pass out the error, which is a better solution in the long term.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
- Mac changes for final release
- Minor fixes to tools configure file
* win/tclWinSock.c: Apply patch to allow write access to a socket
if FD_WRITE is sent but FD_CONNECT is not. Some strange problem
with either Win32 or a socket driver. [Bug: 1664 1776]
|
| | |
|
| |
|
