Author: wayland
Date: 2009-02-26 11:00:39 +0100 (Thu, 26 Feb 2009)
New Revision: 25578
Modified:
docs/Perl6/Spec/S29-functions.pod
docs/Perl6/Spec/S32-setting-library/IO.pod
Log:
S29: Fix formatting
IO.pod: Get rid of tree, spec stat and LinkNode a bit better
Modified:
On Wed, 25 Feb 2009, Larry Wall wrote:
On Thu, Feb 26, 2009 at 02:05:28PM +1100, Timothy S. Nelson wrote:
Does this mean that $! is a container of some sort?
It's an object, which (in the abstract) can contain anything it jolly
well pleases. The main question beyond that is how it
Author: wayland
Date: 2009-02-26 11:57:19 +0100 (Thu, 26 Feb 2009)
New Revision: 25580
Modified:
docs/Perl6/Spec/S28-special-names.pod
Log:
Added types to main table
Modified: docs/Perl6/Spec/S28-special-names.pod
===
---
Author: wayland
Date: 2009-02-26 12:04:54 +0100 (Thu, 26 Feb 2009)
New Revision: 25581
Modified:
docs/Perl6/Spec/S29-functions.pod
docs/Perl6/Spec/S32-setting-library/Containers.pod
Log:
Moved Junctions from S29 to Containers.pod
Modified: docs/Perl6/Spec/S29-functions.pod
Author: wayland
Date: 2009-02-26 12:05:45 +0100 (Thu, 26 Feb 2009)
New Revision: 25582
Modified:
docs/Perl6/Spec/S28-special-names.pod
Log:
Updated main table; refactoring after previous additions
Modified: docs/Perl6/Spec/S28-special-names.pod
On Thu, 26 Feb 2009, Timothy S. Nelson wrote:
My suggested solution would be to change $! to an exception container
object. But then we have to use it in the implicit given in the CATCH block.
If we used an any() Junction, would that do what we want?
Ok, Moritz told me on IRC that this
Em Qui, 2009-02-26 às 22:26 +1100, Timothy S. Nelson escreveu:
given(any(@!)) {
}
using junctions on exception handling doesn't seem like a good idea to
me, because it is too much of a basic feature... but...
for @! {
}
might provide the needed semantics...
OTOH, I think it would be sane to
Em Qui, 2009-02-26 às 08:55 -0300, Daniel Ruoso escreveu:
for @! {}
might provide the needed semantics...
After sending this mail I've just realized I don't know exactly which
are the needed semantics...
what happens if you have several unthrown exceptions in the block, does
it throw every one
Author: wayland
Date: 2009-02-26 13:04:15 +0100 (Thu, 26 Feb 2009)
New Revision: 25583
Added:
docs/Perl6/Spec/S32-setting-library/Callable.pod
Modified:
docs/Perl6/Spec/S32-setting-library/Containers.pod
docs/Perl6/Spec/S32-setting-library/Exception.pod
On Thu, 26 Feb 2009, Daniel Ruoso wrote:
Em Qui, 2009-02-26 às 08:55 -0300, Daniel Ruoso escreveu:
for @! {}
might provide the needed semantics...
After sending this mail I've just realized I don't know exactly which
are the needed semantics...
what happens if you have several unthrown
Author: wayland
Date: 2009-02-26 13:15:04 +0100 (Thu, 26 Feb 2009)
New Revision: 25584
Modified:
docs/Perl6/Spec/S32-setting-library/Containers.pod
Log:
Container.pod fixes, based on IRC advice.
Modified: docs/Perl6/Spec/S32-setting-library/Containers.pod
Author: wayland
Date: 2009-02-26 13:24:08 +0100 (Thu, 26 Feb 2009)
New Revision: 25585
Added:
docs/Perl6/Spec/S32-setting-library/Abstraction.pod
Modified:
docs/Perl6/Spec/S32-setting-library/Containers.pod
Log:
Containers.pod: Got some composition straightened out
Abstraction.pod:
HaloO,
Larry Wall wrote:
That seems a bit ugly though. Another way would be to define ± as
simple half-open Range and then overload comparison:
multi sub infix:==(Num $x,Range $r) {
$x == any($r.minmax);
}
This is strange. Having 1 == 1..3 and 3 == 1..3 as true is
not what I
HaloO,
Jon Lang wrote:
@a[50%] # accesses the middle item in the list, since Whatever is
set to the length of the list.
I don't understand what you mean with setting Whatever. Whatever is
a type that mostly behaves like Num and is used for overloaded
postcircumfix:[ ]:(Array @self:
Em Qui, 2009-02-26 às 17:01 +0100, TSa escreveu:
$y.error = 0.001;
$x ~~ $y;
Looking at this I just started wondering... why wouldn't that be made
with:
my $y = 10 but Imprecise(5%);
$x ~~ $y;
daniel
Author: lwall
Date: 2009-02-26 17:37:55 +0100 (Thu, 26 Feb 2009)
New Revision: 25591
Modified:
docs/Perl6/Spec/S03-operators.pod
Log:
1-ary values for chaining operators should always be True even if negated
Modified: docs/Perl6/Spec/S03-operators.pod
TSa wrote:
HaloO,
Jon Lang wrote:
�...@a[50%] # accesses the middle item in the list, since Whatever is
set to the length of the list.
I don't understand what you mean with setting Whatever. Whatever is
a type that mostly behaves like Num and is used for overloaded
postcircumfix:[
Daniel Ruoso wrote:
Em Qui, 2009-02-26 às 17:01 +0100, TSa escreveu:
$y.error = 0.001;
$x ~~ $y;
Looking at this I just started wondering... why wouldn't that be made
with:
my $y = 10 but Imprecise(5%);
$x ~~ $y;
That's not bad; I like it.
--
Jonathan Dataweaver Lang
On 2009 Feb 26, at 13:00, Jon Lang wrote:
I'm not sold on the notion that Num should represent a range of values
Arguably a range is the only sane meaning of a floating point number.
--
brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allb...@kf8nh.com
system administrator
I don't know how relevant this is; but this sounds like the sort of
optimization that pure functional programming allows for - that is, if
the compiler ever sees a call like asin(sin($x)), it might optimize
the code by just putting $x in there directly, and bypassing both the
sin and asin calls -
Jon Lang wrote:
TSa wrote:
Jon Lang wrote:
�...@a[50%] # accesses the middle item in the list, since Whatever is
set to the length of the list.
I don't understand what you mean with setting Whatever. Whatever is
a type that mostly behaves like Num and is used for overloaded
On Feb 26, 2009, at 14:27 , Jon Lang wrote:
Jon Lang wrote:
Brandon S. Allbery wrote:
Jon Lang wrote:
I'm not sold on the notion that Num should represent a range of
values
Arguably a range is the only sane meaning of a floating point number.
Perhaps; but a Num is not necessarily a
Martin D Kealey wrote:
On Thu, 26 Feb 2009, Jon Lang wrote:
asin is not the inverse function of sin, although it's probably as close
as you can get. And even there, some sort of compiler optimization could
potentially be done, replacing the composition of asin and sin (both of
which have the
Author: wayland
Date: 2009-02-27 03:44:46 +0100 (Fri, 27 Feb 2009)
New Revision: 25601
Modified:
docs/Perl6/Spec/S03-operators.pod
docs/Perl6/Spec/S29-functions.pod
docs/Perl6/Spec/S32-setting-library/Callable.pod
docs/Perl6/Spec/S32-setting-library/Containers.pod
Here's my comments on Carl Masak's S29 list. Note that some of the
things that say that they're now in something still need a lot of work.
# Range objects have .from, .to, .min, .max and .minmax methods
Now in S32/Containers.pod
# .contains on Hash and Array
Where's this from?
#
On 2009-Feb-26, at 7:46 pm, Timothy S. Nelson wrote:
# Object has .print and .say.
[...]
My question is, would we be better off having the string conversion
routine for arrays worry about the input/output record/field
separators, rather than the IO object? The downside I can see is
that
On Thu, 26 Feb 2009, Martin D Kealey wrote:
On Wed, 25 Feb 2009, Timothy S. Nelson wrote:
I'm in favour of retaining the $[ functionality, but lets give it some
name like $*INDEX_BEGINNING or something like that, so that it's quite
long for people to type :).
Surely the interpretation of
Apologies to Carl Masak for writing his name in ASCII.
# context().
Added to S29, but I still don't know where these should go. Maybe on
Block?
# .wrap, .unwrap and .assuming.
Added to S32/Callable.
# callsame, callwith, nextsame, nextwith, lastcall.
Didn't know where
Author: wayland
Date: 2009-02-27 04:58:37 +0100 (Fri, 27 Feb 2009)
New Revision: 25602
Added:
docs/Perl6/Spec/S32-setting-library/Rules.pod
Modified:
docs/Perl6/Spec/S29-functions.pod
docs/Perl6/Spec/S32-setting-library/Callable.pod
docs/Perl6/Spec/S32-setting-library/Containers.pod
On Thu, 26 Feb 2009, pugs-comm...@feather.perl6.nl wrote:
+The exceptions are:
+
+ Signal Action R Comment
+ --
+ ControlExceptionSigHUPTerm? Hangup detected on controlling terminal
or death of
On Thu, 26 Feb 2009, David Green wrote:
On 2009-Feb-26, at 7:46 pm, Timothy S. Nelson wrote:
# Object has .print and .say.
[...]
My question is, would we be better off having the string conversion routine
for arrays worry about the input/output record/field separators, rather
than the IO
Author: lwall
Date: 2009-02-27 08:42:32 +0100 (Fri, 27 Feb 2009)
New Revision: 25609
Modified:
docs/Perl6/Spec/S06-routines.pod
Log:
typo
Modified: docs/Perl6/Spec/S06-routines.pod
===
--- docs/Perl6/Spec/S06-routines.pod
32 matches
Mail list logo
