On behalf of the Parrot team, I'm proud to announce Parrot 2.10.1
(bugfix release). Parrot (http://parrot.org/) is a virtual machine
aimed at running all dynamic languages.
Parrot 2.10.1 is available on Parrot's FTP site, or by following the
download instructions at http://parrot.org/download.
On Wed, 17 Nov 2010, Richard Hainsworth wrote:
Once a number has been generated, viz., by obtaining a duration, that number
can be manipulated however necessary. The interpretation of the number is a
matter for the programmer, not the language designer.
All true.
However I'd argue that you
On 11/17/2010 10:08 PM, Martin D Kealey wrote:
Dimensioned numbers as restrictive types are useful, for uncovering bugs,
including sometimes latent ones in ported code.
Duration is a fairly clear example of a dimensioned quantity, and I think we
should think twice about abandoning its
Here's my proposal for how to handle dimensionality in Perl 6:
Create a units trait that is designed to attach to any Numeric
object. Dimensional information gets stored as a baggy object - that
is, something that works just like a Bag, except that the count can
go negative. (I don't know if
At 16:58 -0800 11/18/10, Jon Lang wrote:
If this is implemented, Duration should be an alias for something to
the effect of Num but unitssecond. Otherwise, Instant and
Duration remain unchanged.
Thoughts?
http://www.physics.nist.gov/cuu/Units/index.html
with special attention to:
I think that Instant and Duration should simply be declarational roles that
don't have any implementation code to compose.
Composing Instant or Duration into a type simply says that the objects of
that type represent a point on a timeline or an amount of time.
Specific units, even seconds
To clarify, by define particular methods I mean that said 2 roles would
require composing classes to define them, not to include the code themselves. --
Darren Duncan
Darren Duncan wrote:
I think that Instant and Duration should simply be declarational
roles that don't have any implementation
Jon ():
Here's my proposal for how to handle dimensionality in Perl 6:
[...]
Thoughts?
The idea has come up before, everyone thinks that Perl 6 and unit
handling are a good fit for each other, and we're basically waiting
for someone to write such a module. Incidentally, your phrase a
Darren ():
Specific units, even seconds should not be mentioned at all in the
definition of Instant or Duration; instead, any particular units or
calendars or whatever would just be a property of the composing class.
No disrespect, but it was the abandonment of abstracty stuff like this
that
On Thu, Nov 18, 2010 at 8:25 PM, Carl Mäsak cma...@gmail.com wrote:
Jon ():
Here's my proposal for how to handle dimensionality in Perl 6:
[...]
Thoughts?
The idea has come up before, everyone thinks that Perl 6 and unit
handling are a good fit for each other, and we're basically waiting
Jon Lang asked me if I intended to send this message to him privately.
The answer is No...
-- Forwarded message --
From: Buddha Buck blaisepas...@gmail.com
Date: Thu, Nov 18, 2010 at 10:39 PM
Subject: Re: dimensionality in Perl 6
To: Jon Lang datawea...@gmail.com
On Thu, Nov
Buddha Buck wrote:
Jon Lang wrote:
Here's my proposal for how to handle dimensionality in Perl 6:
Create a units trait that is designed to attach to any Numeric
object. Dimensional information gets stored as a baggy object - that
is, something that works just like a Bag, except that the
Jon (), Carl (), Jon ():
Here's my proposal for how to handle dimensionality in Perl 6:
[...]
Thoughts?
The idea has come up before, everyone thinks that Perl 6 and unit
handling are a good fit for each other, and we're basically waiting
for someone to write such a module. Incidentally,
On Thu, Nov 18, 2010 at 11:53 PM, Jon Lang datawea...@gmail.com wrote:
Buddha Buck wrote:
I don't think a Num is necessary, but I could see a Rat.
As is, is Duration implemented by means of a Num, or a Rat? Whichever
it is, that's the type that the difference of two Instances would
return
Carl Mäsak wrote:
Darren ():
Specific units, even seconds should not be mentioned at all in the
definition of Instant or Duration; instead, any particular units or
calendars or whatever would just be a property of the composing class.
No disrespect, but it was the abandonment of abstracty
15 matches
Mail list logo
