# New Ticket Created by Mike Lambert
# Please include the string: [perl #809]
# in the subject line of all future correspondence about this issue.
# http://bugs6.perl.org/rt2/Ticket/Display.html?id=809 >
Okay, patch is included below. Here are the relevant times from the gc
bench suite:
gc_a
Ask Bjoern Hansen wrote:
> [EMAIL PROTECTED] (John Porter) writes:
>
> > Yeah, look at the so-called Parrot FAQ. Someone needs to
> > get serious and make a real FAQ for parrot developers.
>
> I'm sure noone would mind if you start one!
Does no one on this mailing see my point?
It does not w
On Sat, 13 Jul 2002, John Porter wrote:
>
> Ask Bjoern Hansen wrote:
> > [EMAIL PROTECTED] (John Porter) writes:
> >
> > > Yeah, look at the so-called Parrot FAQ. Someone needs to
> > > get serious and make a real FAQ for parrot developers.
> >
> > I'm sure noone would mind if you start one!
>
>
On Sat, Jul 13, 2002 at 06:41:22AM -0700, John Porter wrote:
> channel. For all I know, there are no frequently asked
> questions on the irc channel. For all I know, there are no
> newbie parrot developers on the channel.
Having read but deleted rather too much of this thread to respond to the
On Sat, Jul 13, 2002 at 03:48:31PM +0100, Nicholas Clark wrote:
> I was working somewhere where the chief technical architect, a very smart
> guy, was far too busy doing stuff to write it down, and also didn't view it
> as a priority as "I don't need to write it down, it's all in my head".
And on
In message <20020712010920$[EMAIL PROTECTED]>
Simon Glover (via RT) <[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Simon Glover
> # Please include the string: [netlabs #789]
> # in the subject line of all future correspondence about this issue.
> # http://bugs6.perl.org/rt2/Tick
Okay, it's reasonably obvious that we're lacking in documentation in
spots, and it's also reasonably obvious that we need to fix that.
Docs for the source need to be forthcoming, so we'll work on that.
It's also pretty obvious that people have questions and the FAQ isn't
sufficient. So lets fi
On Saturday 13 July 2002 07:39 am, Sean O'Rourke wrote:
> To help even more, you could collect the answers to these questions when
> you receive them, and make the resulting FAQ part of your contribution to
> Parrot. Write the FAQ you wish had existed when you first came.
I would find that handy
In message <20020712005836$[EMAIL PROTECTED]>
Simon Glover (via RT) <[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Simon Glover
> # Please include the string: [netlabs #790]
> # in the subject line of all future correspondence about this issue.
> # http://bugs6.perl.org/rt2/Tick
In message <20020711221132$[EMAIL PROTECTED]>
Simon Glover (via RT) <[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Simon Glover
> # Please include the string: [netlabs #788]
> # in the subject line of all future correspondence about this issue.
> # http://bugs6.perl.org/rt2/Tick
In message <20020703012231$[EMAIL PROTECTED]>
Simon Glover (via RT) <[EMAIL PROTECTED]> wrote:
> This code:
>
> A:# prints "a"
> print "a"
> end
>
> doesn't assemble; the assembler dies with the error message:
>
> Use of uninitialized value in hash el
In message <20020703015823$[EMAIL PROTECTED]>
Simon Glover (via RT) <[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Simon Glover
> # Please include the string: [netlabs #758]
> # in the subject line of all future correspondence about this issue.
> # http://bugs6.perl.org/rt2/Tick
On Sat, 2002-07-13 at 12:32, Tom Hughes wrote:
> In message <20020703012231$[EMAIL PROTECTED]>
> Simon Glover (via RT) <[EMAIL PROTECTED]> wrote:
>
> > This code:
> >
> > A:# prints "a"
> > print "a"
> > end
> >
> > doesn't assemble; the assembler dies wit
In message <20020713174114$[EMAIL PROTECTED]>
brian wheeler <[EMAIL PROTECTED]> wrote:
> On Sat, 2002-07-13 at 12:32, Tom Hughes wrote:
> > In message <20020703012231$[EMAIL PROTECTED]>
> > Here's a patch that will fix this. I havn't committed it because I'm
> > not sure why the assembe
Here's the code I have:
open I0, "test.txt", "<"
open I1, "testdtxt", "<"
end
I assemble and load it into pdb and get this:
Parrot Debugger 0.0.1
(pdb) list
1 open_i_sc_sc I0,"test.txt<","<"
2 open_i_sc_sc I1,"testdtxt","<"
3 end
(pdb)
The first one is listed as "test.txt<" instead of "t
Hi,
Its been a long time since I've posted anything to this list, mainly because
my company graciously gave me 1 1/2 years to get a Ph.D. as long as I agreed
to work full time too :) (and by the way I don't have a masters :) So, I've
been very busy. Nevertheless, I saw the recent complaints abo
Nicholas Clark wrote:
>
>An IRC channel is good for discussions. But it doesn't archive them,
>index them, collate them and provide them as reference for any new
>would be recruits. I'm not saying that anyone has to write the docs, or
>even the skeleton of the docs for their code - everyone and a
In message <[EMAIL PROTECTED]>
Bryan Logan <[EMAIL PROTECTED]> wrote:
> Here's the code I have:
>
> open I0, "test.txt", "<"
> open I1, "testdtxt", "<"
> end
>
> I assemble and load it into pdb and get this:
>
> Parrot Debugger 0.0.1
>
> (pdb) list
> 1 open_i_sc_sc I0,"test.txt<","
On gcc we turn on -Wpadded
In file included from include/parrot/interpreter.h:46,
from include/parrot/parrot.h:114,
from register.c:13:
include/parrot/op.h:80: warning: padding struct to align `arg_count'
which is this:
typedef struct {
op_type_t type;
Jim Cromie sent the following bits through the ether:
> can we could invent a super-lightweight markup language
> that #parrot-eers would type into the stream to put meta-info into it ?
OK, I'll finally join this discussion. Yes, IRC is handy for realtime
questions like (just an example as it ha
20 matches
Mail list logo
