Adam Kennedy wrote:
* has_pod_index: The POD contains at least one X<> keyword that helps
POD indexers. Whether only one is usefull is open for debate, because
at least the license (X), your CPAN ID under authors (x),
and some generic keyword what your module (X) is about can
probably added eve
On Mon, Nov 07, 2005 at 01:05:16PM +0100, TSa wrote:
: With the introduction of kind capture variables ^T we could complety
: drop the subtype special form. As you pointed out the adding of constraints
: happens with the where clause anyway. Thus we return to the usage of the
: compile time name as
All~
On 11/6/05, Joshua Juran <[EMAIL PROTECTED]> wrote:
> On Nov 5, 2005, at 4:27 PM, Joshua Hoblitt via RT wrote:
>
> >> [EMAIL PROTECTED] - Tue Nov 01 04:52:22 2005]:
> >>
> >> This patch fixes two classes of issue.
> >>
> >> * Don't assign -1 to an unsigned variable; use ~0U instead as it
>
On Monday 07 November 2005 09:26 am, Rob Kinyon wrote:
> On 11/7/05, Michele Dondi <[EMAIL PROTECTED]> wrote:
> > On Fri, 4 Nov 2005, Rob Kinyon wrote:
> > > So, for a bit of extra complexity, I get peace of mind for myself and
> > > my users.
> >
> > The point being, and I'm stressing it once agai
On Mon, Nov 07, 2005 at 09:37:04AM -0800, Larry Wall wrote:
: It would be nice to generalize this sufficiently to be able to declare
: polymorphic objects resembling match objects:
:
:my $matchobj(Poly: Key^Int^Notthere --> Any);
:
: Or maybe that should be:
:
:my $matchobj\(Highlander)
On 2005-11-07 1:30 PM, "Andrew Rodland" <[EMAIL PROTECTED]> wrote:
> Especially when that complexity isn't optional. I
> think that's really a common "fear", that Perl 6 is going well beyond that
> point of sensibility.
>
> If you want to get into personal beliefs, I think that function signatures
In p6rules, how should specify characters (glyphs, bytes, whatever)
using octal notation?
Currently S02 says that integer constants in octal are written with
as "0o" prefix (as in 0o123), just as we would use the "0x" prefix
to specify integers using base-16.
It doesn't seem to be written anywher
On Mon, Nov 07, 2005 at 10:51:59AM -0600, Patrick R. Michaud wrote:
: In p6rules, how should specify characters (glyphs, bytes, whatever)
: using octal notation?
:
: Currently S02 says that integer constants in octal are written with
: as "0o" prefix (as in 0o123), just as we would use the "0x" pr
On Sun, Nov 06, 2005 at 11:31:37PM +1100, Andrew Savige wrote:
: On revisiting the old p6 golf example programs of *cough* six
: months ago, I noticed they all still worked save one:
:
: [=<>].reverse.print
:
: This used to reverse the lines in a file, but now prints the
: lines unreversed and wi
HaloO,
Larry Wall wrote:
> : ::Takes3Ints ::= :(Int,Int,Int --> Any);
> :
> : my &foo:(Takes3Ints);
>
> I'd say that has to be something like:
>
> my &foo:(Takes3Ints:);
>
> or maybe one of
>
> my &foo:(Takes3Ints \!);
> my &foo:(\Takes3Ints);
> my &foo\(Takes3Ints);
>
On Sun, Nov 06, 2005 at 03:10:40PM +0100, Ingo Blechschmidt wrote:
: Hi,
:
: my ($key, $value) = ;
: my $pair = ($key => $value);
:
: $pair.key = "new";
: # Should this fail ("cannot modify a constant")?
: # Should this update $pair.key, but leave $key untouched?
:
On Mon, Nov 07, 2005 at 11:53:26AM -0800, Larry Wall wrote:
: Also, if we provide a way to return a pair instead of a value from a
: hash (currently done with the new :%hash syntax),
Whoops, I forgot I changed that to %hash: (and %hash:{'key'} too).
Larry
On Mon, Nov 07, 2005 at 11:13:21AM -0800, Larry Wall wrote:
> On Mon, Nov 07, 2005 at 10:51:59AM -0600, Patrick R. Michaud wrote:
> : It doesn't seem to be written anywhere, but I think it's assumed
> : that in string literals one would use "\o123", just as we use
> : "\x0a".
>
> That should cert
On Mon, Nov 07, 2005 at 02:18:24PM -0600, Patrick R. Michaud wrote:
: Having a shortcut for seems like a very good idea; it
: certainly makes things a lot simpler for the optimizer. However,
: a reminder that A05 says that angles can be used as a bracketing
: construct as in C<< \x<0a> >>, so we
On Mon, Nov 07, 2005 at 02:18:24PM -0600, Patrick R. Michaud wrote:
: Ick, \d65 in a pattern looks really odd to me. I'll register my
: distaste for this one message, and then I'll have to take a stiff
: drink or something before I can bring myself to implement it. :-|
I suppose we could even go
Hi,
Larry Wall wrote:
> On Sun, Nov 06, 2005 at 03:10:40PM +0100, Ingo Blechschmidt wrote:
[ => should not automatically bind its .value to the RHS ]
> I think binding directly to .key or .value is different from what =>
> does. So after
>
> $pair = $key => $value;
>
> setting $value doesn
Andrew Rodland skribis 2005-11-07 13:30 (-0500):
> If you want to get into personal beliefs, I think that function signatures
> are
> such a complexity quagmire -- and that they're line-noise ugly to boot.
The nice thing about signatures is that they let you write what you
mean. This saves you a
On Mon, Nov 07, 2005 at 09:51:39PM +0100, Juerd wrote:
: Or let's take this simple example:
:
: sub convert (:$from, :$to, :$thing) { ... }
:
: That isn't quite "my %args = @_;". Yes, that works, but the only real
: way we keep doing it is that the full solution sucks in plain Perl 5:
:
:
> Okay, I won't shout (not even on PerlMonks :-), but named parameters
> default to optional, so you'd have to write that as
>
> sub convert (:$from!, :$to!, :$thing!) { ... }
>
> in the current scheme of things.
Either way, the point is still that the benefits FAR outweigh any
additional comp
On Monday 07 November 2005 03:51 pm, Juerd wrote:
> Andrew Rodland skribis 2005-11-07 13:30 (-0500):
> > If you want to get into personal beliefs, I think that function
> > signatures are such a complexity quagmire -- and that they're line-noise
> > ugly to boot.
>
> The nice thing about signatures
On Mon, Nov 07, 2005 at 04:46:06PM -0500, Andrew Rodland wrote:
> Sorry, I wasn't clear here, so I hope you don't mind my cutting you off. What
> I meant wasn't "signatures are too much complexity" -- they're not; they're
> simply doing something useful -- but rather "too much complexity is getti
I've had this problem for awhile with a distribution I've been working
on where sometimes, after invoking Makefile.PL, typing 'make' creates a
blib folder with all of the .exists files in the right places, but
doesn't copy the actual module files to it.
This was driving me crazy. I don't have a s
On Mon, Nov 07, 2005 at 12:05:30PM -0800, Larry Wall wrote:
> On Mon, Nov 07, 2005 at 11:53:26AM -0800, Larry Wall wrote:
> : Also, if we provide a way to return a pair instead of a value from a
> : hash (currently done with the new :%hash syntax),
>
> Whoops, I forgot I changed that to %hash: (an
On Mon, Nov 07, 2005 at 12:37:02PM -0800, Larry Wall wrote:
> On Mon, Nov 07, 2005 at 02:18:24PM -0600, Patrick R. Michaud wrote:
> : Having a shortcut for seems like a very good idea; it
> : certainly makes things a lot simpler for the optimizer. However,
> : a reminder that A05 says that angles
On Mon, Nov 07, 2005 at 11:20:39PM +0200, Ilmari Vacklin wrote:
: On Mon, Nov 07, 2005 at 12:05:30PM -0800, Larry Wall wrote:
: > On Mon, Nov 07, 2005 at 11:53:26AM -0800, Larry Wall wrote:
: > : Also, if we provide a way to return a pair instead of a value from a
: > : hash (currently done with th
-BEGIN PGP SIGNED MESSAGE-
Moin Rob,
On Monday 07 November 2005 23:22, Rob Bloodgood wrote:
> I've had this problem for awhile with a distribution I've been working
> on where sometimes, after invoking Makefile.PL, typing 'make' creates a
> blib folder with all of the .exists files in the
On Mon, Nov 07, 2005 at 02:47:05PM -0600, Patrick R. Michaud wrote:
: > : But for the :w issue, we can always solve it with the colon:
: > :
: > : \d:065 = A digit (cut) followed by "065"
: >
: > That doesn't extend to \d:woot, of course...
:
: It doesn't? I mean, isn't that a digit fol
Larry Wall skribis 2005-11-07 13:20 (-0800):
> Okay, I won't shout (not even on PerlMonks :-), but named parameters
> default to optional, so you'd have to write that as
> sub convert (:$from!, :$to!, :$thing!) { ... }
> in the current scheme of things.
Ah, thanks.
I hadn't noticed this chang
# New Ticket Created by Allison Randal
# Please include the string: [perl #37633]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37633 >
One thing that would be nice is a bit of PIR syntactic sugar for
if_null and unless
Adam Kennedy wrote:
> Doesn't makemaker only like you if you have a single .pm file just in
> the root directory?
>
> And otherwise you have to have your lib files actually under lib?
>
> lib/Tree/Splay.pm
> lib/Tree/Splay/Node.pm
> lib/Tree/Splay/IntRange.pm
> t/01_basics.t
> t/02_compat.t
> Mak
"Allison Randal (via RT)" <[EMAIL PROTECTED]> wrote:
One thing that would be nice is a bit of PIR syntactic sugar for
if_null and unless_null opcodes. Maybe something like:
if null $P5 goto LABEL
unless null $P5 goto LABEL
Done, enjoy.
Thanks,
Jonathan
Rob Bloodgood wrote:
Adam Kennedy wrote:
Doesn't makemaker only like you if you have a single .pm file just in
the root directory?
And otherwise you have to have your lib files actually under lib?
lib/Tree/Splay.pm
lib/Tree/Splay/Node.pm
lib/Tree/Splay/IntRange.pm
t/01_basics.t
t/02_compat.t
* has_pod_index: The POD contains at least one X<> keyword that helps
POD indexers. Whether only one is usefull is open for debate, because
at least the license (X), your CPAN ID under authors (x),
and some generic keyword what your module (X) is about can
probably added even for the most minima
HaloO,
Stevan Little wrote:
This is actually the principe behind the Ruby style singleton methods
(the shadow class), it basically creates an anon-class which inherits
from $x's original class, then it rebinds/blesses $x into the anon-
class. It is very simple really :)
Yes, it's the typic
HaloO,
Larry Wall wrote:
: or is 'bound of' proper english?
It doesn't really resonate for a native speaker.
--snip--
: > Plus, as we've defined
: >them above, subtypes are the most generic type you can name in Perl.
--snip--
I wasn't using the term "generic" in a type-theoretic sense.
# New Ticket Created by Nick Glencross
# Please include the string: [perl #37627]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37627 >
In r9815 I believe there to be a rare problem with the memory allocation
during regi
Nick Glencross (via RT) wrote:
In r9815 I believe there to be a rare problem with the memory allocation
during register colouring.
The code is assuming that a maximum of unit->n_symbols exist, but will
step outside this range in rare circumstance. The memory allocation and
initially setting
Adam Kennedy wrote:
* has_pod_index: The POD contains at least one X<> keyword that helps
POD indexers. Whether only one is usefull is open for debate, because
at least the license (X), your CPAN ID under authors (x),
and some generic keyword what your module (X) is about can
probably added eve
On Fri, 4 Nov 2005, Juerd wrote:
Whatever, the new system by contrast seems to me to be at least 400%
more complex, but it won't buy me 400% more functionality.
It will buy you 400% in saving typing, 4000% in less debubbing and
4% in maintainability(==readability).
Of course drawing any
On 11/7/05, Michele Dondi <[EMAIL PROTECTED]> wrote:
> On Fri, 4 Nov 2005, Rob Kinyon wrote:
>
> > So, for a bit of extra complexity, I get peace of mind for myself and my
> > users.
>
> The point being, and I'm stressing it once again but no more than once,
> that maybe we're adding two bits of ex
40 matches
Mail list logo
