Pugs and Elf currently numify a Pair object to 2, and Rakudo currently
dies of despair.
My guess is that the semantics of Pugs and Elf falls out naturally
form a pair being treated as a list of two elements, or something. The
question still deserves to be raised whether always-2 is a good
HaloO,
Carl Mäsak wrote:
Pugs and Elf currently numify a Pair object to 2, and Rakudo currently
dies of despair.
My guess is that the semantics of Pugs and Elf falls out naturally
form a pair being treated as a list of two elements, or something. The
question still deserves to be raised
HaloO,
Darren Duncan wrote:
Michael G Schwern wrote:
TSa (Thomas Sandlaß) wrote:
I want to stress this last point. We have the three types Int,
Rat and Num. What exactly is the purpose of Num? The IEEE formats
will be handled by num64 and the like. Is it just there for
holding properties? Or
Hi all,
I've been thinking about how the IO interface should be organized in
perl6. It seems that part of S16 has received little attention so far.
One main problem with filehandles is that are rather diverse. The only
operation that all of them have in common is close. Reading versus
writing is
Leon Timmermans wrote:
What I propose is using role composition for *everything*. Most
importantly that includes the roles Readable and Writable, but also
things like Seekable, Mapable, Pollable, Statable, Ownable, Buffered
(does Readable), Socket, Acceptable (does Pollable), and more.
That
On 2008 Dec 11, at 20:16, Leon Timmermans wrote:
One main problem with filehandles is that are rather diverse. The only
operation that all of them have in common is close. Reading versus
Be glad Xenix is dead. There were filehandles which didn't even
support close() (they were actually
On Thu, Dec 11, 2008 at 8:16 PM, Leon Timmermans faw...@gmail.com wrote:
What I propose is using role composition for *everything*. Most
importantly that includes the roles Readable and Writable, but also
things like Seekable, Mapable, Pollable, Statable, Ownable, Buffered
(does Readable),
