In the #concatenative channel recently, a user complained about not being able
to find documentation for the in a TUPLE: declaration. Of course, this is
covered in the documentation for TUPLE: itself, but when you see a tuple
definition in the listener, the , unlike most syntactic elements,
W dniu 22.09.2010 16:36, Doug Coleman pisze:
Hi,
I recently made it a requirement that a server either start on all the ports
specified or none of them. The server code attempts to bind to and
immediately close an ipv6 port, and if it's successful, a server will also
bind ipv6. Binding
(...) listening on ip6 port. So, there's an issue with concurrent threads.
listening on separate address spaces.
D.
... on the same port (I mean as numeric value). Experimentally, I've
changed set-servers to mutate ip6 address port (+1) and threads had no
problems with start. Up and
On Thu, Sep 23, 2010 at 10:48 PM, Joe Groff arc...@gmail.com wrote:
I think this behavior would also suit closing delimiters, such as }, ],
;, and so on. The documentation for these words themselves is pretty
useless—usually, people are going to want to see the documentation for the
actual
On Thu, Sep 23, 2010 at 04:18:37PM +0530, Joe Groff wrote:
In summary, any syntactic token should link to the docs of the main
syntactic form it is a part of. What do you guys think?
Sounds good to me.
Miles
--
So you've got to know that *synergy* doesn't actually mean *synergy* in
this
