The issue of having an :init pragma for subs came up again during
today's #parrotsketch meeting, and I volunteered to summarize the
discussion for ticket #39926 and the mailing list.
The :init pragma is intended to make it easier for automatically
generated modules to make sure that
this is too noisy as ~700 tests. please convert it to one test, like the
other coding standard tests.
Ok. Have changed it to be the same as the other coding standard
tests. See attached patch.
also, it should apply to perl files, as well. in fact, it should
probably apply to most files in
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #40560]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40560
Hi,
This patch gets regex/lib/Regex/Grammar.y to pass the
HaloO,
Jonathan Lang wrote:
If at all possible, I would expect Complex to compose Num, thus
letting a Complex be used anywhere that a Num is requested.
This will not work. The Num type is ordered the Complex type isn't.
The operators , =, and = are not available in Complex. Though
I can
HaloO Jonathan,
you wrote:
I think I found the core of the issue here; it has to do with the
differences between roles and mixins, with an analogous difference
between compile-time composition and runtime composition. Details
follow.
I think we are basically through the discussion. Thank you
TSa wrote:
Jonathan Lang wrote:
If at all possible, I would expect Complex to compose Num, thus
letting a Complex be used anywhere that a Num is requested.
This will not work. The Num type is ordered the Complex type isn't.
The operators , =, and = are not available in Complex.
They can
On Wed, Oct 18, 2006 at 06:55:16AM -0700, Jonathan Lang wrote:
TSa wrote:
Jonathan Lang wrote:
If at all possible, I would expect Complex to compose Num, thus
letting a Complex be used anywhere that a Num is requested.
This will not work. The Num type is ordered the Complex type isn't.
Nicholas Clark wrote:
Jonathan Lang wrote:
They can be:
$A $B if $A.x $B.x | $A.y $B.y;
$A $B if $A.x $B.x | $A.y $B.y;
This also allows you to unambiguously order any arbitrary set of
complex numbers.
If I'm reading that correctly then there are values of $A and $B for which
$A
TSa wrote:
you wrote:
I think I found the core of the issue here; it has to do with the
differences between roles and mixins, with an analogous difference
between compile-time composition and runtime composition. Details
follow.
I think we are basically through the discussion. Thank you
-- Original message --
From: Jonathan Lang [EMAIL PROTECTED]
TSa wrote:
Jonathan Lang wrote:
If at all possible, I would expect Complex to compose Num, thus
letting a Complex be used anywhere that a Num is requested.
This will not work. The Num type is
The attached patch is broken because of lack of flag space.
I coded it up this morning. It wasn't too bad except that we have run
out of PObj flags in which to store sub attributes.
Ideas?
Also how do I get flex and bison to regen the grammar?
I made real clean
perl Configure.pl --maintainer
# New Ticket Created by Jerry Gay
# Please include the string: [perl #40562]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40562
add a command-line option to to t/op/perlcritic.t to display a list of
tested
On Tue, Oct 17, 2006 at 04:22:59PM -0700, Jonathan Lang wrote:
: I've never really been happy with the inconsistency between runtime
: composition and compile-time composition; but my problem has generally
: been with the runtime side of things - in particular, I find the fact
: that does A does B
Am Mittwoch, 18. Oktober 2006 17:20 schrieb Kevin Tew:
Working code with test.
I stole PBC_POSTCOMP's flag for the short term.
That's an unfortunate decision. There are load-time flags and run-time flags.
You can just take one of the runtime-flags. I'd propose you use:
SUB_FLAG_TAILCALL
Thanks I didn't know which flag too pick.
I finally did get flex and bison to run.
Do you thing you could annotate the rest of the flags as to when they
are used?
Kevin
Leopold Toetsch wrote:
Am Mittwoch, 18. Oktober 2006 17:20 schrieb Kevin Tew:
Working code with test.
I stole
Am Mittwoch, 18. Oktober 2006 01:35 schrieb Karl Forner:
Hi,
Is there a way to specify a minimum allocation size for PMCs like strings
or arrays ?
Something like in perl : %h = 1000 ?
It could boost execution times when you have a good idea of the space you
need.
For example, I'd like to
Am Mittwoch, 18. Oktober 2006 20:46 schrieben Sie:
Do you thing you could annotate the rest of the flags as to when they
are used?
typedef enum {
SUB_FLAG_CORO_FF = PObj_private0_FLAG, /* r */
SUB_FLAG_C_HANDLER= PObj_private0_FLAG, r / C exceptions only
Larry Wall wrote:
You've got it inside out. Unordered is just does A | B | C or
some such, the | there really being coerced to a set construction,
not a junction. In fact, would work just as well. I only used |
because it's more readable. Autocoercion of junctions to sets is,
of course,
Author: larry
Date: Wed Oct 18 13:57:40 2006
New Revision: 13210
Modified:
doc/trunk/design/syn/S05.pod
Log:
word boundaries are defined in terms of \w, not \s
Modified: doc/trunk/design/syn/S05.pod
==
---
Mark Biggar wrote:
Jonathan Lang wrote:
They can be:
$A $B if $A.x $B.x | $A.y $B.y;
$A $B if $A.x $B.x | $A.y $B.y;
That dosn't work.
Agreed. The above was written in haste, and contained a couple of
fatal syntax errors that I didn't intend. Try this:
multi infix: =
Author: larry
Date: Wed Oct 18 14:49:21 2006
New Revision: 13211
Modified:
doc/trunk/design/syn/S05.pod
Log:
missing = from particle++
Modified: doc/trunk/design/syn/S05.pod
==
--- doc/trunk/design/syn/S05.pod
# New Ticket Created by Jerry Gay
# Please include the string: [perl #40564]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40564
currently, this policy does not ignore subs which exit or die... it
forces the
Hi, Just checked out parrot and the build failed like this:cc -o miniparrot -L/usr/local/lib -Wl,-E compilers/imcc/main.o \ -Wl,-rpath=/home/kforner/dev/parrot/test/parrot/blib/lib -L/home/kforner/dev/parrot/test/parrot/blib/lib -lparrot -ldl -lm -lpthread -lcrypt -lrt src/null_config.o
-- Original message --
From: Jonathan Lang [EMAIL PROTECTED]
Mark Biggar wrote:
Jonathan Lang wrote:
They can be:
$A $B if $A.x $B.x | $A.y $B.y;
$A $B if $A.x $B.x | $A.y $B.y;
That dosn't work.
Agreed. The above was written in
Though actually, now that I think about it, the cascaded notation
in S12 is illegal according to S03, since does is classified as
non-chaining, which implies non-associative. Hmm. We'd have to make
it right associative somehow. Put it in with ** maybe?
Hmm.
Or leave it non-associative and
On Wed, Oct 18, 2006 at 01:32:14PM -0700, Jonathan Lang wrote:
: The | notation is mentioned in S012:1029, by the way. Obviously you
: still haven't quite memorized all the synopses. :-)
:
: Actually, I was very well aware of that fact.
Oops, didn't realize you were suggesting a semantic
Yeah, I caused this.
Patch Applied
Kevin
Karl Forner wrote:
Hi,
Just checked out parrot and the build failed like this:
cc -o miniparrot -L/usr/local/lib -Wl,-E compilers/imcc/main.o \
-Wl,-rpath=/home/kforner/dev/parrot/test/parrot/blib/lib
Larry Wall wrote:
Though actually, now that I think about it, the cascaded notation
in S12 is illegal according to S03, since does is classified as
non-chaining, which implies non-associative. Hmm. We'd have to make
it right associative somehow. Put it in with ** maybe?
Hmm.
Or leave it
28 matches
Mail list logo
