A question.
In a project of mine I'm looking to use Perl 6 Range values to represent
continuous interval values in the most generic manner possible, meaning that the
endpoint values could literally be of any type at all.
I just wanted to confirm that that would work in the general case,
Author: pmichaud
Date: 2009-10-04 16:26:35 +0200 (Sun, 04 Oct 2009)
New Revision: 28589
Modified:
docs/Perl6/Spec/S08-capture.pod
Log:
[S08]: Some notes where online discussions are at odds with the spec.
Modified: docs/Perl6/Spec/S08-capture.pod
Author: pmichaud
Date: 2009-10-04 16:27:33 +0200 (Sun, 04 Oct 2009)
New Revision: 28590
Modified:
docs/Perl6/Spec/S08-capture.pod
Log:
[S08]: Update mime-type for .pod document.
Property changes on: docs/Perl6/Spec/S08-capture.pod
Author: pmichaud
Date: 2009-10-04 16:28:27 +0200 (Sun, 04 Oct 2009)
New Revision: 28591
Modified:
docs/Perl6/Spec/S08-capture.pod
Log:
[S08]: Update svn:eol-style property.
Property changes on: docs/Perl6/Spec/S08-capture.pod
Hi Darren.
Darren Duncan wrote:
In a project of mine I'm looking to use Perl 6 Range values to
represent continuous interval values in the most generic manner
possible, meaning that the endpoint values could literally be of any
type at all. [...] for a realistic example:
my $a = ['Foo',
I'm confused between using ranges to generate a lazy list and using
them as criteria to match against.
These exclude continuous (non-countable) types-
...
2. There must be a successor function, so that given an object from
the given domain, say a, successor(a) returns one and only one
On Oct 4, 2009, at 12:47 PM, yary wrote:
There was a big discussion about this on the list recently but I don't
recall the resolutions.
The resolution was r28344: http://dev.pugscode.org/changeset/28344.
The short version is that ranges are now primarily used for testing
inclusion in
Author: moritz
Date: 2009-10-04 19:15:29 +0200 (Sun, 04 Oct 2009)
New Revision: 28595
Modified:
docs/Perl6/Spec/S03-operators.pod
Log:
[S03] thinko
Modified: docs/Perl6/Spec/S03-operators.pod
===
---
Author: moritz
Date: 2009-10-04 19:15:43 +0200 (Sun, 04 Oct 2009)
New Revision: 28596
Modified:
docs/Perl6/Spec/S03-operators.pod
Log:
[S03] be more consequent in removing :by
Modified: docs/Perl6/Spec/S03-operators.pod
===
---
Author: moritz
Date: 2009-10-04 19:15:53 +0200 (Sun, 04 Oct 2009)
New Revision: 28597
Modified:
docs/Perl6/Spec/S32-setting-library/Numeric.pod
Log:
[S32/Numeric] major overhaul
* Most methods that were in Num are now Numeric
* sign() and the rounding methods are now in Real
* document (at
yary wrote:
I'm confused between using ranges to generate a lazy list and using
them as criteria to match against.
Indeed. It was my understanding that there was a recent change to
Ranges so that they now exist primarily to be used as matching
criteria. If you wish to generate a list, the
How do pred and succ work when given Complex values?
More generally: if Complex does Numeric, then Numeric doesn't include
Ordered (or whatever it's called), because Complex doesn't do Ordered.
As such, you can't used Numeric for any function that depends on the
value being Ordered.
On Sun, Oct
Jon Lang wrote:
How do pred and succ work when given Complex values?
By adding/substracting 1 from the real part, I'd say. Don't know if that
actually makes sense.
More generally: if Complex does Numeric, then Numeric doesn't include
Ordered (or whatever it's called), because Complex doesn't
Moritz Lenz wrote:
Jon Lang wrote:
How do pred and succ work when given Complex values?
By adding/substracting 1 from the real part, I'd say. Don't know if that
actually makes sense.
It doesn't, because succ should always give the next, smallest possible
element given some ordering
Michael Zedeler wrote:
Moritz Lenz wrote:
Jon Lang wrote:
How do pred and succ work when given Complex values?
By adding/substracting 1 from the real part, I'd say. Don't know if that
actually makes sense.
It doesn't, because succ should always give the next, smallest possible
Moritz Lenz wrote:
Jon Lang wrote:
typos: s[Nuermic] = Numeric
You do have a pugs commit bit, don't you?
A what? AFAICT, I don't have any way of editing the Synopses; all I
can do is to comment on what I find.
--
Jonathan Dataweaver Lang
Jon Lang wrote:
Moritz Lenz wrote:
Jon Lang wrote:
typos: s[Nuermic] = Numeric
You do have a pugs commit bit, don't you?
A what? AFAICT, I don't have any way of editing the Synopses;
You have now (sorry for assuming earlier that you had). A username and
password should be on the way to
Minimiscience wrote:
On Oct 4, 2009, at 12:47 PM, yary wrote:
There was a big discussion about this on the list recently but I don't
recall the resolutions.
The resolution was r28344: http://dev.pugscode.org/changeset/28344.
The short version is that ranges are now primarily used for
Darren Duncan wrote:
However, I still don't see how one would retrieve the distinction between say
1..10 and 1^..^10. I suggest that an extra 2 methods such as
.min_is_outside and .max_is_outside (each returns a Bool) could fit the bill,
and in fact since I have Pugs write access I think
Author: Darren_Duncan
Date: 2009-10-04 23:36:46 +0200 (Sun, 04 Oct 2009)
New Revision: 28612
Modified:
docs/Perl6/Spec/S03-operators.pod
Log:
Spec S03 : add Range methods .excl_min, .excl_max
Modified: docs/Perl6/Spec/S03-operators.pod
Moritz Lenz wrote:
Darren Duncan wrote:
However, I still don't see how one would retrieve the distinction between say
1..10 and 1^..^10. I suggest that an extra 2 methods such as
.min_is_outside and .max_is_outside (each returns a Bool) could fit the bill,
and in fact since I have Pugs write
21 matches
Mail list logo
