r26034 - docs/Perl6/Spec/S32-setting-library

2009-03-30 Thread pugs-commits
Author: wayland Date: 2009-03-31 07:07:01 +0200 (Tue, 31 Mar 2009) New Revision: 26034 Modified: docs/Perl6/Spec/S32-setting-library/IO.pod Log: S32/IO: Based on some suggestions of bacek++ and skids++, I refined the initialisation of the $.Listening attribute. This may need more discussion

r26033 - docs/Perl6/Spec/S32-setting-library

2009-03-30 Thread pugs-commits
Author: wayland Date: 2009-03-31 06:29:09 +0200 (Tue, 31 Mar 2009) New Revision: 26033 Modified: docs/Perl6/Spec/S32-setting-library/IO.pod Log: S32/IO: Added a .new() method to IO::Socket::Unix Modified: docs/Perl6/Spec/S32-setting-library/IO.pod =

r26032 - docs/Perl6/Spec/S32-setting-library

2009-03-30 Thread pugs-commits
Author: wayland Date: 2009-03-31 06:22:47 +0200 (Tue, 31 Mar 2009) New Revision: 26032 Modified: docs/Perl6/Spec/S32-setting-library/IO.pod Log: S32/IO: Made calls to .new() a bit more consistent with each other. Modified: docs/Perl6/Spec/S32-setting-library/IO.pod =

Re: Junction Algebra

2009-03-30 Thread Martin Kealey
On Mon, 30 Mar 2009, Mark J. Reed wrote: > >        ( $a <= any(-1,+1) <= $b ) == ( $a <= any(-1,+1) && any(-1,+1) <= $b > > ) > > Clearly, the RHS is true for $a == $b == 0, but I'm not sure the LHS > shouldn't also be. Isn't it just syntactic sugar for the RHS? I suspect not. Rather I think th

Re: Junction Algebra

2009-03-30 Thread Mark J. Reed
On Mon, Mar 30, 2009 at 9:44 PM, Martin D Kealey wrote: > This would certainly be false: > >        ( $a <= any(-1,+1) <= $b ) == ( $a <= any(-1,+1) && any(-1,+1) <= $b ) Clearly, the RHS is true for $a == $b == 0, but I'm not sure the LHS shouldn't also be. Isn't it just syntactic sugar for the

Re: Junction Algebra

2009-03-30 Thread Martin D Kealey
On Mon, 30 Mar 2009, Jon Lang wrote: > Here's another useful one: > > any($x) eqv all($x) eqv one($x) eqv $x > > but: > > none($x) !eqv $x > > That is, applying any, all, or one to a one-item list produces the > equivalent to a single item. For an empty list: any() eqv all() eqv > (). But

r26031 - docs/Perl6/Spec/S32-setting-library

2009-03-30 Thread pugs-commits
Author: wayland Date: 2009-03-31 02:48:54 +0200 (Tue, 31 Mar 2009) New Revision: 26031 Modified: docs/Perl6/Spec/S32-setting-library/IO.pod Log: S32/IO: Expanded IO::Socket, mostly at the expense of IO::Socket::INET. Modified: docs/Perl6/Spec/S32-setting-library/IO.pod =

r26030 - docs/Perl6/Spec/S32-setting-library

2009-03-30 Thread pugs-commits
Author: wayland Date: 2009-03-31 02:30:46 +0200 (Tue, 31 Mar 2009) New Revision: 26030 Modified: docs/Perl6/Spec/S32-setting-library/IO.pod Log: S32/IO: - Merged IO::Listening into IO::Socket - Made IO::Socket implement IO::Closeable - Added a $.Listening attribute to IO::Sock

Re: Junction Algebra

2009-03-30 Thread Jon Lang
Here's another useful one: any($x) eqv all($x) eqv one($x) eqv $x but: none($x) !eqv $x That is, applying any, all, or one to a one-item list produces the equivalent to a single item. For an empty list: any() eqv all() eqv (). But what about one() and none()? -- Jonathan "Dataweaver

Re: On Junctions

2009-03-30 Thread Jon Lang
On Sun, Mar 29, 2009 at 10:57 PM, Mark Lentczner wrote: > What I see here is that there is a tendency to want to think about, and > operate on, the eigenstates as a Set, but this seems to destroy the "single > value" impersonation of the Junction. In my case, this tendency comes more from a desir

r26025 - docs/Perl6/Spec/S32-setting-library

2009-03-30 Thread pugs-commits
Author: wayland Date: 2009-03-30 15:01:45 +0200 (Mon, 30 Mar 2009) New Revision: 26025 Modified: docs/Perl6/Spec/S32-setting-library/IO.pod Log: S32/IO.pod: Changed "TCP" to "INET" Modified: docs/Perl6/Spec/S32-setting-library/IO.pod ===

Re: On Junctions

2009-03-30 Thread Daniel Ruoso
Em Dom, 2009-03-29 às 22:57 -0700, Mark Lentczner escreveu: > What I see here is that there is a tendency to want to think about, > and operate on, the eigenstates as a Set, but this seems to destroy > the "single value" impersonation of the Junction. > Further, if one ever calls .!eigenstates(