# New Ticket Created by "Clinton A. Pierce"
# Please include the string: [netlabs #700]
# in the subject line of all future correspondence about this issue.
# http://bugs6.perl.org/rt2/Ticket/Display.html?id=700 >
After correcting the build problem with MSVC (stock MSVC++ 6.0, AS Perl,
etc.
Andy Wardley <[EMAIL PROTECTED]> writes:
> On Sat, Jun 08, 2002 at 06:51:19AM +1000, Damian Conway wrote:
>> I have no doubt that, once Perl 6 is available, we'll see a rash of
>> modules released in the Grammar:: namespace. Including
>> Grammar::HTML and Grammar::XML.
>
> I have no doubt that, o
At 10:54 PM 6/10/2002 +, you wrote:
># New Ticket Created by "Clinton A. Pierce"
># Please include the string: [netlabs #700]
># in the subject line of all future correspondence about this issue.
># http://bugs6.perl.org/rt2/Ticket/Display.html?id=700 >
>
>
>After correcting the build proble
# New Ticket Created by "Clinton A. Pierce"
# Please include the string: [netlabs #702]
# in the subject line of all future correspondence about this issue.
# http://bugs6.perl.org/rt2/Ticket/Display.html?id=702 >
To reproduce, sync with CVS, build, run "basic.pl" -- that's all. This
versi
On Tue, 2002-06-11 at 01:38, Dan Sugalski wrote:
> (A note--when this says "stack" I really mean all the stacks)
>
> Okay, I've been thinking about stacks and stack frames, and suchlike
> things. Well, calling them "stacks" is a bit of a misnomer, since
> they're really trees, and that's partia
A5 says this:
> I'm accepting the basic premise of this RFC that the ?...? construct is
> going away, one way or another.
and perlop (from 5.6.1) says this:
> ?PATTERN?
> ...
> This usage is vaguely deprecated, which means it just might possibly
> be removed in some distant future v
I've added Gcd and factorial to core.ops, see attachement.
Dan is this something you want?
I also have "least common multiple" and "binomial" implementation
waiting. If you want them i can can make a patch
/Josef
--- core.ops.orig Tue Jun 11 10:03:19 2002
+++ core.opsTue Jun 11 1
On Mon, 10 Jun 2002, Jeff wrote:
> Tests are now failing because of the removal of the 'inc_n_ic' opcode. I
> find this interesting for several reasons. One, the tests probably
> should have been removed. Two, once the 'inc' operator has two
> parameters, it is no longer 'increment' in my mind. I
I've added Gcd and factorial to core.ops, as attachement.
Dan is this something you want?
I also have "least common multiple" and "binomial" implementation
waiting. If you want them i can can make a patch
/Josef
--- core.ops.orig Tue Jun 11 10:03:19 2002
+++ core.opsTue Jun 11
At 8:22 AM -0400 6/11/02, Bryan C. Warnock wrote:
>On Tue, 2002-06-11 at 01:38, Dan Sugalski wrote:
>> (A note--when this says "stack" I really mean all the stacks)
>>
>> Okay, I've been thinking about stacks and stack frames, and suchlike
>> things. Well, calling them "stacks" is a bit of a mi
At 9:50 AM -0500 6/11/02, David M. Lloyd wrote:
>The question is, do we want all combos of i,p, and n? So add_i_i, add_n_i,
>add_p_i, add_i_n, add_n_n, add_p_n, add_i_p, add_n_p, add_p_p? Or is this
>too many ops?
I'm OK with the combos, with the caveat that we may remove them if it
turns out l
On Tue, Jun 11, 2002 at 11:31:37AM -0400, Dan Sugalski wrote:
> We'll find out with A6 whether we do coroutines and continuations as
> part of the core perl. If not, well, python does the first and ruby
> the second, so it's all good in there.
Does anyone feel like giving a 1 paragraph potted
At 05:07 PM 6/11/2002 +0100, Dave Mitchell wrote:
>On Tue, Jun 11, 2002 at 11:31:37AM -0400, Dan Sugalski wrote:
> > We'll find out with A6 whether we do coroutines and continuations as
> > part of the core perl. If not, well, python does the first and ruby
> > the second, so it's all good in the
At 12:29 PM 6/11/2002 -0400, Melvin Smith wrote:
You can think of continuations as an execution "context". This context
>incudes everything, not just stack. It is a snapshot in time. You may think
Let me rephrase. The context doesn't include "everything", rather everything
that is local to that c
There's enough words and definitions going by that not everyone
understands that it's time for us to have a glossary.
I'm willing to do the administrative work of maintaining it, if others
send me entries.
So... if there are words you think should be in the parrot glossary
(the recent discussio
At 1:07 PM +0200 6/11/02, =?latin1?Q?Josef_H=F6=F6k?= wrote:
>
>I've added Gcd and factorial to core.ops, as attachement.
>Dan is this something you want?
>I also have "least common multiple" and "binomial" implementation
>waiting. If you want them i can can make a patch
I like it, but I think I
> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> We'll find out with A6 whether we do coroutines and continuations as
DS> part of the core perl. If not, well, python does the first and ruby
DS> the second, so it's all good in there.
on the last perl cruise, i had a nice talk wit
> > > Dave Storrs wrote:
> > > Can we please have a 'reverse x' modifier that means "treat whitespace as
> > > literals"? Yes, we are living in a Unicode world now and your data could
> > >
> > > /FATAL ERROR\:Process (\d+) received signal\: (\d+)/
> >
> > I don't see how this example is near
Josef Höök wrote:
>
> I've added Gcd and factorial to core.ops, see attachement.
> Dan is this something you want?
> I also have "least common multiple" and "binomial" implementation
> waiting. If you want them i can can make a patch
>
> /Josef
How are we going to get people to write recursive
"Clinton A. Pierce (via RT)" wrote:
> No warnings during compilation, no errors.
>
> The error reported for each test is:
>
> Parrot VM: Can't unpack packfile .pbc
Same here (on Linux):
http://www.sebastian-bergmann.de/stuff/parrot_test.txt
--
Sebastian Bergmann
http://s
At 5:07 PM +0100 6/11/02, Dave Mitchell wrote:
>On Tue, Jun 11, 2002 at 11:31:37AM -0400, Dan Sugalski wrote:
>> We'll find out with A6 whether we do coroutines and continuations as
>> part of the core perl. If not, well, python does the first and ruby
>> the second, so it's all good in there.
21 matches
Mail list logo
