Re: [perl #39426] [BUG] Can't build with cygwin.

2007-06-16 Thread Paul Cochrane

Paul Cochrane wrote:
 Without the manual setting of PATH before building?

 With the manual PATH setting.  There are several tickets for cygwin
 not building in RT; are they all related?  Is there something like a
 hints file where the information about the PATH can be set so that
 cygwin builds out of the box?


Cygwin is building for me without the PATH setting as of r19022.  Are
other people seeing this behaviour as well?  If so, can we get rid of
the (three or four) parrot isn't building on cygwin tickets in RT?

Paul


Re: [perl #41569] t/distro/file_metadata.t fails on win32

2007-06-16 Thread Paul Cochrane

Ron,


 I simple changed the backward slashes to forward slashes, thus forward
 slashes everywhere.

 Which was what *I* intended to do with my patch, but after staring at
 it long enough, I realised that's not what *it* was saying!  :-)
 Ooops.

Oh, I see.  Sorry I didn't get this right.


That's ok!  No need to apologise.  I was only pointing out what I was
misunderstanding :-)


 Ron, would it be ok if you could check the patch to see if it works on
 Win32?  Thanks heaps in advance.

There's one piece missing:  You'd need to splitdir/catdir $directories
too, otherwise it's left as-is.

I have attached a modified patch, and prove-ed it works with r18945 on
Win32.


I couldn't get your patch to apply cleanly and so hacked it in by
hand.  I'm attaching a new patch to this email (which is quite
possibly identical to yours) so that you can give it a quick test.  If
all is happy, then I'll commit the change and close the ticket.

Thanks heaps for your help!

Paul


file_metadata.patch
Description: Binary data


[perl #43227] [PATCH] lua - cleanup of temporary files

2007-06-16 Thread via RT
# New Ticket Created by  Paul Cochrane 
# Please include the string:  [perl #43227]
# in the subject line of all future correspondence about this issue. 
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=43227 


I've not really hacked much pir before so I thought instead of
committing this patch, I'd send it to the list for review first (I
learn very slowwwly ;-) ).  It attempts to clean up the temporary
files generated by the lua test suite, which leaves a lot of its files
clogging up the main parrot dir.  This patch reduces the problem.

Comments welcome!

Paul


lua_temp_cleanup.patch
Description: Binary data


Parrot in hardware

2007-06-16 Thread GDR!
Hi,

  I'm new here so I'll say hello - I'm GDR!.
  I was looking at the Parrot project recently and I'd like to
implement the VM in hardware. I'm not deeply into the project,
however,  so I'd like to ask you if the Parrot bytecode is now stable
enough to begin hardware developement - I wouldn't like to end up with
a chip supporting some pre-historical version of VM.

-- 
C'ya - GDR! \ Luciddreams EntertainmentJABBERID: [EMAIL PROTECTED]
SMS:+48 51 666 15 05
http://gdr.geekhood.net/

If you talk to God, you are praying; if God talks to you, you have 
schizophrenia. - Thomas Szasz



Re: [perl #39426] [BUG] Can't build with cygwin.

2007-06-16 Thread Eric Hanchrow
 Paul == Paul Cochrane [EMAIL PROTECTED] writes:

Paul Cygwin is building for me without the PATH setting as of
Paul r19022.  

Not for me, alas:

$ svn up -r19022
$ perl Makefile.PL 
$ make all 
...

Invoking Parrot to generate runtime/parrot/include/config.fpmc --cross your 
fingers
./miniparrot.exe config_lib.pasm  runtime/parrot/include/config.fpmc
make: *** [runtime/parrot/include/config.fpmc] Error 53

-- 
I'm a libertarian with a fascist heart.
-- Jim Blandy



[perl #43230] Parrotcode.org

2007-06-16 Thread via RT
# New Ticket Created by  GDR! 
# Please include the string:  [perl #43230]
# in the subject line of all future correspondence about this issue. 
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=43230 


Hi,

  I tried to subscribe to the Parrot list, however the address
  supplied doesn't work ([EMAIL PROTECTED] ) - the
  mails keep bouncing.  I've been informed  on IRC that the proper address is
  [EMAIL PROTECTED] Would be nice if this is updated
  :)

-- 
C'ya - GDR! \ Luciddreams EntertainmentJABBERID: [EMAIL PROTECTED]
SMS:+48 51 666 15 05
http://gdr.geekhood.net/

Ubuntu to staroafrykańskie słowo, które znaczy Nie potrafię zainstalować i 
skonfigurować Debiana.



[perl #31980] Factorial example gives incorrect result

2007-06-16 Thread Allison Randal via RT
On Mon Feb 20 16:23:46 2006, jhoblitt !-- x -- at hawaii.edu wrote:
 On Tue, Feb 21, 2006 at 01:03:59AM +0100, Leopold Toetsch wrote:
  
  On Feb 20, 2006, at 23:44, Joshua Hoblitt via RT wrote:
  
  What happened to the factorial PASM example?  It seems to have
  disappeared and it hasn't re-appeared as a PIR example either.
  
  It used bogus high numbers beyond int32 range and was just broken.
 
 Only because it was using integer registers.  Limiting it to low
 factorial values or using Integer pmcs would resolve the issue.  I'm
 going to add a PIR example using Integer pmcs unless there are any
 objections.

Did you add the examples? I'd like to close the ticket.

Allison


[perl #43231] [BUG] :slurpy :named after :optional fails

2007-06-16 Thread via RT
# New Ticket Created by  Patrick R. Michaud 
# Please include the string:  [perl #43231]
# in the subject line of all future correspondence about this issue. 
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=43231 


Defining a .sub with both :optional (positional) and :slurpy :named
parameters results in an exception invalid arg type in 
named portion of args when called without the optional arg.

Example:

$ cat x.pir
.sub 'main' :main
'foo'(123, 'xyz' = 'abc')
'foo'('xyz' = 'abc')
.end

.sub 'foo'
.param string posarg   :optional
.param inthas_posarg   :opt_flag
.param pmcnamedargs:slurpy :named
say posarg
$S0 = namedargs['xyz']
say $S0
.return()
.end

$ ./parrot x.pir
123
abc
invalid arg type in named portion of args
current instr.: 'foo' pc 26 (x.pir:7)
called from Sub 'main' pc 21 (x.pir:3)
$
  
I've entered a (TODO) test for this into t/op/calling.t,
and will cite this RT# in the test (as soon as I have it).

Thanks!

Pm