This really belongs to perl6-internals and not perl6-language.
On 28 Aug 2002 at 17:19, Sean O'Rourke wrote:
> On Thu, 29 Aug 2002, Markus Laire wrote:
> > (only 32bit numbers, modulo not fully working, no capturing regexps,
> > )
>
> Where does modulo break?
Modulo is currently defined fo
> Codename Octarine
>
> Schedule as follows:
>
> August 29, 8am EDT: Code slush, only bug and warning fixes allowed.
> August 30, 11:59pm EDT: Code freeze and pretag
> August 31, 00:59 EDT: Tag and Release
Is there any reason to not to use GMT times in general? I have hard
time remembering all
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #16838]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16838 >
Hi,
during hacking on imcc and testing with life.p6 I found wrong core.ops
of type
# New Ticket Created by Jürgen Bömmels
# Please include the string: [perl #16839]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16839 >
Hi!
This MANIFEST things come up again and again. This time there are 5
missing file
On Wed, Aug 28, 2002 at 10:36:54AM -0700, Larry Wall wrote:
> That is a worthy consideration, but expressiveness takes precedence
> over it in this case. DFAs are really only good for telling you
> *whether* and *where* a pattern matches as a whole. They are
> relatively useless for telling you
A question: Do rules matched in a { code } block set backtrack points for
the outer rule? For example, are these rules equivalent?
rule expr1 {
{ /@operators/ or fail }
}
rule expr2 {
@operators
}
And a comment: It would be nice to have procedural control over back-
tracking
> The ° character doesn't have any special meaning,
> that's why I choosed it in the above example.
> However, it also symbolizes a little capturing
> and as it isn't filled,
> it could really symbolize an uncapturing.
Interesting idea. I'm not sure if I agree with it yet. However, I don't
agr
On Thu, 2002-08-29 at 08:05, Ken Fox wrote:
> A question: Do rules matched in a { code } block set backtrack points for
> the outer rule? For example, are these rules equivalent?
>
> rule expr1 {
> { /@operators/ or fail }
> }
>
> rule expr2 {
> @operators
> }
>
> And a comm
Aaron Sherman wrote:
> rule { { /@operators/.commit(1) or fail } }
>
> The hypothetical commit() method being one that would take a number and
That would only be useful if the outer rule can backtrack into the
inner /@operators/ rule. Can it?
I agree with you that a commit method woul
# New Ticket Created by Andy Bussey
# Please include the string: [perl #16842]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16842 >
I am compiling Parrot under Solaris 8 using gcc.
- I get lots of warnings about
"padd
Hi,
examples/life-ar.p6 uses a rather lengthy initialisation
my @world = (
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
...
}; # 512 values
then tries to figure out, how many generations to run:
my $gen = @ARGS[0] || 512;
at this point, @ARGS[0] aka P0[1] aka argv[1] is
From: Dan Sugalski [EMAIL PROTECTED]
>I actually had something a bit more subversive
>in mind, where the assignment operator for the
>Date class did some magic the same way we do
>now when we do math on strings.
I was thinking a simple general purpose rule. If the variable is
typed, and its class
On Thu, 2002-08-29 at 10:28, Ken Fox wrote:
> Aaron Sherman wrote:
> > rule { { /@operators/.commit(1) or fail } }
> >
> > The hypothetical commit() method being one that would take a number and
>
> That would only be useful if the outer rule can backtrack into the
> inner /@operators/
On Thu, Aug 29, 2002 at 07:52:42AM -0700, Steve Canfield wrote:
> From: Dan Sugalski [EMAIL PROTECTED]
> >I actually had something a bit more subversive
> >in mind, where the assignment operator for the
> >Date class did some magic the same way we do
> >now when we do math on strings.
>
> I was t
Luke Palmer wrote at Thu, 29 Aug 2002 15:21:57 +0200:
>> The ° character doesn't have any special meaning,
>> that's why I choosed it in the above example.
>> However, it also symbolizes a little capturing
>> and as it isn't filled,
>> it could really symbolize an uncapturing.
>
> Interesting id
# New Ticket Created by Steve Fink
# Please include the string: [perl #16851]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16851 >
This patch disables the possibly spurious warnings reported by
GC_DEBUG when walking the
# New Ticket Created by Steve Fink
# Please include the string: [perl #16852]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16852 >
This patch trims off the period at the end of executable filenames for
C-based tests on u
On Thu, 29 Aug 2002, Andy Bussey wrote:
> I am compiling Parrot under Solaris 8 using gcc.
>
> - I get lots of warnings about
> "padding struct to align 'whatever'"
> "padding struct size to alignment boundary" etc
Yes, there are lots of warnings. It's probably the case that some are
harml
# New Ticket Created by Steve Fink
# Please include the string: [perl #16853]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16853 >
This patch makes re-running Configure.pl avoid updating the timestamps
on the generated .
# New Ticket Created by Steve Fink
# Please include the string: [perl #16854]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16854 >
I forget what this was testing, but it uncovered a problem at some
point in the past.
# New Ticket Created by Steve Fink
# Please include the string: [perl #16855]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16855 >
In tracking down a gc bug, I realized that the current throwaway
implementation of the pr
Bryan C. Warnock writes:
>How does one patch a file to delete?
>
>docs/a5_draft.html can go away now, thank you for playing.
rm
cvs delete
cvs commit
# New Ticket Created by Steve Fink
# Please include the string: [perl #16856]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16856 >
I was once idly toying with imcc while awaiting a phone call. This is
the completely unte
On Thu, Aug 29, 2002 at 01:05:33PM -0700, Robert Spier wrote:
> Bryan C. Warnock writes:
> >How does one patch a file to delete?
> >
> >docs/a5_draft.html can go away now, thank you for playing.
>
> rm
> cvs delete
> cvs commit
Not if you don't have commit access! :-)
You can diff against /de
# New Ticket Created by Steve Fink
# Please include the string: [perl #16857]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16857 >
Small cleanups, but also a piece of my attempted fixes to the
BUFFER_external_FLAG. (The
# New Ticket Created by Steve Fink
# Please include the string: [perl #16858]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16858 >
Oops, this should have been combined with the previous dod.c patch.
It's the same thing -
Bryan C. Warnock writes:
>There is a general inconsistency about file permissions throughout the
>parrot tree.
>
>Of the 80+ *.pl scripts, only 8 are 0755 - and Configure.pl isn't one of
>them. Some tests are, some aren't; and even some docs are. A list
>follows.
These have to be fixed in the re
# New Ticket Created by Steve Fink
# Please include the string: [perl #16859]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16859 >
This patch is the real fix for strings with the BUFFER_external_FLAG.
It requires the pre
# New Ticket Created by Steve Fink
# Please include the string: [perl #16860]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=16860 >
As a result of my recent changes to debug.c, a plain 'p' (or 'print')
in pdb now seg faul
I ran some quick time tests on the GC, and hashes are relatively
expensive to GC, relative to other things. (They're an order of
magnitude slower than perlstrings, and two orders of magitude slower
than perlints) They're slow enough that I'd like to take a look at
them to see if perhaps there'
On Thu, 29 Aug 2002, Robert Spier wrote:
> Bryan C. Warnock writes:
> >There is a general inconsistency about file permissions throughout the
> >parrot tree.
> >
> >Of the 80+ *.pl scripts, only 8 are 0755 - and Configure.pl isn't one of
> >them. Some tests are, some aren't; and even some docs ar
On Thu, 29 Aug 2002, Steve Fink wrote:
> - Adds %option nounput to imcc.l. This avoids a warning when
>compiling the output file. This one is correct, at least.
Hmm. Sun's lex(1) doesn't understand that line. Is there another easy
way around the problem? If not, I'll try to think of some
On Thu, Aug 29, 2002 at 04:31:14PM -0400, Dan Sugalski wrote:
> I ran some quick time tests on the GC, and hashes are relatively
> expensive to GC, relative to other things. (They're an order of
> magnitude slower than perlstrings, and two orders of magitude slower
> than perlints) They're slow
On Thu, Aug 29, 2002 at 04:48:20PM -0400, Andy Dougherty wrote:
> On Thu, 29 Aug 2002, Steve Fink wrote:
>
> > - Adds %option nounput to imcc.l. This avoids a warning when
> >compiling the output file. This one is correct, at least.
>
> Hmm. Sun's lex(1) doesn't understand that line. Is t
Don't forget you can parameterize rules with subrules. I don't see
any reason you couldn't write a
kind of rule and do whatever you like with the submatched bits.
Larry
On Thu, 29 Aug 2002, Thomas A. Boyer wrote:
: Am I getting this straight?
As straight as any of us are getting it thus far. :-)
The process is intended to be convergent. That doesn't guarantee it
will converge, but that's the intention.
When I'm playing golf, I always expect to knock the ball
At 02:06 PM 8/29/2002 -0700, Steve Fink wrote:
>On Thu, Aug 29, 2002 at 04:48:20PM -0400, Andy Dougherty wrote:
> > On Thu, 29 Aug 2002, Steve Fink wrote:
> >
> > > - Adds %option nounput to imcc.l. This avoids a warning when
> > >compiling the output file. This one is correct, at least.
> >
Steve Fink (via RT) wrote:
> This patch trims off the period at the end of executable filenames for
> C-based tests on unix.
Nice, but I'm a little bit Warnocked.
1) I did post a script (testnative), which runs _all_ tests as
executables, _all_ not one, and --shared too.
2) Im my tree (~2
On Thu, Aug 29, 2002 at 11:56:42PM +0200, Leopold Toetsch wrote:
> Steve Fink (via RT) wrote:
>
> >This patch trims off the period at the end of executable filenames for
> >C-based tests on unix.
>
> Nice, but I'm a little bit Warnocked.
>
> 1) I did post a script (testnative), which runs _all
Larry wrote:
> sub while (&test is rx//, &body);
>
> or some such. That probably isn't sufficient to pick out of Perl's
> grammar rather than the current lexical scope.
I love the idea, but the property name needs to be more expressive
(and Huffmanly longer). Maybe:
sub while (
Ken Fox wrote:
> A question: Do rules matched in a { code } block set backtrack points for
> the outer rule?
I don't believe so. From A5:
A pattern nested within a closure is classified as its own rule,
however, so it never gets the chance to pass out of a {...} closure.
Indee
41 matches
Mail list logo
