trunk/languages/forth/words.pir
trunk/runtime/parrot/library/Range.pir
trunk/t/compilers/imcc/syn/hll.t
trunk/t/library/p6object.t
trunk/t/oo/isa.t
trunk/t/pmc/key.t
trunk/t/pmc/multidispatch.t
trunk/t/pmc/namespace.t
trunk/t/pmc/parrotinterpreter.t
trunk/t/pmc/threads.t
Log
If someone could untangle this inadvertent commit to a tag instead of
trunk, I'd appreciate it.
On Wed, Oct 22, 2008 at 1:40 PM, <[EMAIL PROTECTED]> wrote:
> Author: coke
> Date: Wed Oct 22 10:40:50 2008
> New Revision: 32110
>
> Modified:
> tags/RELEASE_0_8
On Fri, Oct 03, 2008 at 01:23:14AM -0700, [EMAIL PROTECTED] wrote:
> +parrotclass = split '::', $S0
> +$P0 = getinterp
> +$P0 = $P0['namespace';1]
> +$P0 = $P0.get_name()
> +$P0 = shift $P0
> +unshift parrotclass, $P0
> +parrotclass = get_root_namespace [parrotclass]
Th
On Sat, Sep 13, 2008 at 02:30:30PM +0200, Jonathan Worthington wrote:
>>> (2) Test.pm gets Object rather than Any on its multis; this may or
>>> may not be the Right Thing.
>> perl6-language may end up disagreeing with me on this, but I would
>> much prefer things (from a implementation boots
Yay...verbose commit messages = I can haz useful input. :-)
Patrick R. Michaud wrote:
On Fri, Sep 12, 2008 at 05:03:20PM -0700, [EMAIL PROTECTED] wrote:
[...]
(2) Test.pm gets Object rather than Any on its multis;
this may or may not be the Right Thing.
perl6-language may end up disa
On Fri, Sep 12, 2008 at 05:03:20PM -0700, [EMAIL PROTECTED] wrote:
> [...]
> (2) Test.pm gets Object rather than Any on its multis;
> this may or may not be the Right Thing.
perl6-language may end up disagreeing with me on this, but I would
much prefer things (from a implementation bootstrapping
Author: pmichaud
Date: Mon Jan 21 18:32:45 2008
New Revision: 25116
Modified:
trunk/docs/pdds/pdd26_ast.pod
Changes in other areas also in this revision:
Modified:
trunk/compilers/pct/src/PCT/Node.pir
trunk/runtime/parrot/library/Parrot/Capture_PIR.pir
Log:
[pct]:
* Add shift and pop
On Fri, Jun 29, 2007 at 11:55:28AM -0500, Patrick R. Michaud wrote:
> I just spent about an hour trying to figure out how the files
> in runtime/parrot/library/ are automatically compiled into .pbc files
> when Parrot is built. It turns out that the list of files
> is computed from
I just spent about an hour trying to figure out how the files
in runtime/parrot/library/ are automatically compiled into .pbc files
when Parrot is built. It turns out that the list of files
is computed from the MANIFEST, and I was searching through
files in the config/ subdirectory (where most
Nicholas Clark wrote:
If you're adding before or after an existing named stage, the ambiguity is
to which one you mean. Except having now studied the PIR, I can see that
there isn't ambiguity, because it's "all of them".
There's no test for this though. Hence why I didn't realise.
Good point.
On Fri, Feb 16, 2007 at 12:42:24AM +0200, Allison Randal wrote:
> Nicholas Clark wrote:
> >
> > What happens if you add a stage with the same name as an existing stage?
>
> It gets added twice. You might repeat a stage like "optimize_tree" or
> "display_benchmarks" after each transformation.
>
>
Nicholas Clark wrote:
>
> What happens if you add a stage with the same name as an existing stage?
It gets added twice. You might repeat a stage like "optimize_tree" or
"display_benchmarks" after each transformation.
> Is ambiguity acceptable?
What kind of ambiguity?
Allison
On Thu, Feb 15, 2007 at 09:39:28AM -0800, [EMAIL PROTECTED] wrote:
> +=item addstage(string stagename [, "option" => value, ... ])
> +
> +Add a stage to the compilation process queue. Takes either a "before" or
> +"after" named argument, which gives the relative ordering of the stage
> +to be adde
> Will,
>
> I'm really deeply sorry for reverting stuff with my last commit.
Heh. Things happen. It's ok. Jerry did worse to tcl just before the
release. =-)
I appreciate the fix up. I was a certainly a little grumpy, but it's
fixed, before I even had a chance to sit back down and look at the
co
as chromatic hints at here, you should make sure you have the latest
SVN::Mirror. i know we've seen problems with svk in the past with
empty commit messages, and this was (part of)? the solution.
It seems I had two versions of SVN::Mirror floating around. Version
0.72 (the latest) was in /usr/li
On Jan 19, 2007, at 7:46 AM, Paul Cochrane wrote:
Will,
I'm really deeply sorry for reverting stuff with my last commit.
Heh. Things happen. It's ok. Jerry did worse to tcl just before the
release. =-)
I appreciate the fix up. I was a certainly a little grumpy, but it's
fixed, before I
Paul Cochrane wrote:
Essentially you should svk pull before any commit or push operation,
which helps avoid having to do conflict resolution.
I'm adding in spots in all caps where you should do a svk pull.
Kevin
I'm working from a mirrored copy, and my usual work cycle is:
svk up -sm looks
On 19/01/07, jerry gay <[EMAIL PROTECTED]> wrote:
On 1/19/07, chromatic <[EMAIL PROTECTED]> wrote:
> On Friday 19 January 2007 04:46, Paul Cochrane wrote:
>
> > I wanted to commit a
> > line endings change to shootout.t in lua, but when I went 'svk push' I
> > got an "Empty commit message" error
> I wanted to commit a
> line endings change to shootout.t in lua, but when I went 'svk push' I
> got an "Empty commit message" error again and the only way I know to
> fix this is to use 'svk merge -c //parrot/local/
> //parrot/remote -m "a non-empty commit message"', then it seems to
> commit e
On 1/19/07, chromatic <[EMAIL PROTECTED]> wrote:
On Friday 19 January 2007 04:46, Paul Cochrane wrote:
> I wanted to commit a
> line endings change to shootout.t in lua, but when I went 'svk push' I
> got an "Empty commit message" error again and the only way I know to
> fix this is to use 'svk
On Friday 19 January 2007 04:46, Paul Cochrane wrote:
> I wanted to commit a
> line endings change to shootout.t in lua, but when I went 'svk push' I
> got an "Empty commit message" error again and the only way I know to
> fix this is to use 'svk merge -c //parrot/local/
> //parrot/remote -m "a n
Will,
I'm really deeply sorry for reverting stuff with my last commit. It's
definitely not what I intended. I didn't even edit the tcl (and
other) files, which is what is totally weird. I wanted to commit a
line endings change to shootout.t in lua, but when I went 'svk push' I
got an "Empty co
k: compilers/tge/TGE
languages/tcl/config/makefiles languages/tcl/lib languages/tcl/src
languages/tcl/t runtime/parrot/library/PGE src
Author: paultcochrane
Date: Fri Jan 19 03:06:07 2007
New Revision: 16706
Modified:
trunk/compilers/tge/TGE/Compiler.pir
trunk/languages/tcl/config/makefi
Jonathan Scott Duff wrote:
Is there some reason that runtime/parrot/library isn't in the list of
search paths for both include_paths and dynext_paths?
Fixed.
load_bytecode "PGE.pbc"# should work now
i.e. load_bytecode searches now:
- runtime/parrot/library/
-
Jonathan Scott Duff <[EMAIL PROTECTED]> wrote:
> Is there some reason that runtime/parrot/library isn't in the list of
> search paths for both include_paths and dynext_paths?
No. We have:
load_bytecode => Parrot_load_bytecode
*.pbc => PackFile_appe
Is there some reason that runtime/parrot/library isn't in the list of
search paths for both include_paths and dynext_paths?
-Scott
--
Jonathan Scott Duff
[EMAIL PROTECTED]
On Thu, Nov 11, 2004 at 02:49:24PM +0100, Leopold Toetsch wrote:
> Nicholas Clark wrote:
> >What generates runtime/parrot/library/config.pbc ?
>
> It's an extension rule .imc.pbc.
>
> >It seems that make clean can remove it, and then any subsequent make fails:
>
Nicholas Clark wrote:
What generates runtime/parrot/library/config.pbc ?
It's an extension rule .imc.pbc.
It seems that make clean can remove it, and then any subsequent make fails:
No problem here, jsut tried it.
Nicholas Clark
leo
What generates runtime/parrot/library/config.pbc ?
It seems that make clean can remove it, and then any subsequent make fails:
$ make all
Compiling with:
xx.c
cc -DAPPLLIB_EXP=/usr/local/lib/perl5/5.6.1/BSDPAN -I/usr/local/include -g
-Wall -Wstrict-prototypes -Wmissing-prototypes -Winline
29 matches
Mail list logo
