[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-janitors] #763: posix unit implicitly depends on tcp unit
From: |
Chicken Trac |
Subject: |
Re: [Chicken-janitors] #763: posix unit implicitly depends on tcp unit |
Date: |
Tue, 21 Feb 2012 19:13:35 -0000 |
#763: posix unit implicitly depends on tcp unit
-----------------------------+----------------------------------------------
Reporter: syn | Owner:
Type: defect | Status: new
Priority: major | Milestone: 4.8.0
Component: core libraries | Version: 4.7.x
Resolution: | Keywords:
-----------------------------+----------------------------------------------
Comment(by sjamaan):
I dunno, but this seems awfully hacky of unix-sockets. (just as hacky as
spiffy using the immediate slots of the ssl egg. Guilty as charged! :P)
Unit posix rightfully assumes you shouldn't ever get an object of this
type unless you went through some constructor or other procedure from the
tcp unit. If posix-sockets creates faux tcp ports, it should fix this by
loading the tcp unit, or use some other port type that causes less
problems.
--
Ticket URL: <http://bugs.call-cc.org/ticket/763#comment:1>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Chicken-janitors] #763: posix unit implicitly depends on tcp unit,
Chicken Trac <=