Re: [perl #34258] [TODO] Here documents for PIR

2005-02-25 Thread Leopold Toetsch
Bernhard Schmalhofer <[EMAIL PROTECTED]> wrote: > Hi, > in the near, or far, future there will be test scripts and compiler > input in PIR. For that it would be nice, if long text doesn't have to > be crammed into a single line. > So some kind of HERE document syntax is needed for PIR. Suggesti

Re: How to check an attribute's existence

2005-02-25 Thread Leopold Toetsch
Cory Spencer <[EMAIL PROTECTED]> wrote: > Is is possible to check to see whether an attribute exists on a given > object, or at least catch an exception if it doesn't? I've tried to set > up an exception handler, but Parrot exits without anything being caught. Not yet. C throws currently an unca

Re: [perl #34258] [TODO] Here documents for PIR

2005-02-25 Thread Leopold Toetsch
MrJoltCola <[EMAIL PROTECTED]> wrote: > I feel that this feature is for higher level languages. [ snip ] > ... PIR is for compilers, not people, PIR is foremost Parrot's primary assembly language. If it were for compiles only, it wouldn't have needed "a = b + c" in the first place, the "add" op

[RESENT] (was: [perl #32989] Problem in linux ppc)

2005-02-25 Thread Leopold Toetsch
Leopold Toetsch <[EMAIL PROTECTED]> wrote: I'm still waiting for confirmation that the recipe below works for ppc-linux. Thanks, leo >> jitcapable=1, jitarchname=ppc-linux, > I've now tried to fix that too long lasting problem. > 1) attach the patch below > 2) mv config/gen/platform/darwi

Re: [perl #34258] [TODO] Here documents for PIR

2005-02-25 Thread Roger Browne
MrJoltCola wrote: > This should actually be titled "Where are all the compilers?" The compilers will come! Loads of people, myself included, are quietly working away on compilers that target IMC. It takes time for people to discover and adopt new platforms - especially when you are so modest abou

Re: TAP and STDERR

2005-02-25 Thread Joe Schaefer
[EMAIL PROTECTED] (Michael G Schwern) writes: [...] > More to the point is its completely unstructured output that comes not > as part of the test but between them. It might be worthwhile to associate that "unstructured output" with a particular test (either the previous "ok/not ok" line, or th

Re: [perl #34258] [TODO] Here documents for PIR

2005-02-25 Thread MrJoltCola
At 03:21 AM 2/25/2005, Leopold Toetsch wrote: MrJoltCola <[EMAIL PROTECTED]> wrote: > I feel that this feature is for higher level languages. [ snip ] > ... PIR is for compilers, not people, PIR is foremost Parrot's primary assembly language. If it were for compiles only, it wouldn't have needed "a

Re: [perl #34258] [TODO] Here documents for PIR

2005-02-25 Thread Bernhard Schmalhofer
MrJoltCola wrote: At 03:21 AM 2/25/2005, Leopold Toetsch wrote: MrJoltCola <[EMAIL PROTECTED]> wrote: > I feel that this feature is for higher level languages. [ snip ] > ... PIR is for compilers, not people, My impression was that the target for compilers should be a yet non-existent abstract syn

Q: about Parrot assembly code

2005-02-25 Thread Steve Coleman
Hi, I just came across Parrot the other day, so some of you might think I may have been living under a rock for a little while (and you might not be so wrong either - lol), so please excuse me if I am way out in left field on this topic, but I have a slightly upside down interest in Parrot asm

Re: [perl #34258] [TODO] Here documents for PIR

2005-02-25 Thread MrJoltCola
At 11:48 AM 2/25/2005, Bernhard Schmalhofer wrote: MrJoltCola wrote: At 03:21 AM 2/25/2005, Leopold Toetsch wrote: MrJoltCola <[EMAIL PROTECTED]> wrote: > I feel that this feature is for higher level languages. [ snip ] > ... PIR is for compilers, not people, My impression was that the target for c

Calling C/C++ library routines

2005-02-25 Thread vlad florentino
Hello, I've been developing a compiler that will target Parrot for the last couple of months. I have a question. I've only been reading the list for a short time (1 - 1 1/2 months). I was reading some of the past articles, but there's just so many of them that I figure I might as well just ask the

Re: Q: about Parrot assembly code

2005-02-25 Thread MrJoltCola
At 12:57 PM 2/25/2005, Steve Coleman wrote: constructs that could not be logically mapped from other CPU's into Parrot? Does Parrot assume/use many high level constructs not found in real processors? Some CPU translations, like from CISC to RISC, are clearly easier than the reverse, but other t

Re: Calling C/C++ library routines

2005-02-25 Thread MrJoltCola
At 01:27 PM 2/25/2005, vlad florentino wrote: Is there now, or will there be in the future, any way to call C/C++ library routines from within Parrot? For example, a mysql, pcre or libcurl library. Either static or dynamic. C yes. C shares objects are dynamically loadable by Parrot. C++? Not direct

Re: scoping functions as list operators?

2005-02-25 Thread Aldo Calpini
Stéphane Payrard wrote: # set? I don't think so. my $a, $b, $c set 1..3 ; # alphabetic like and, or, xor? # and what precedence relative to them? well, I'm not sure the feature is good, but I have some idea about the sign that could be used for this :-) we have

Fwd: Calling C/C++ library routines

2005-02-25 Thread vlad florentino
-- Forwarded message -- From: vlad florentino <[EMAIL PROTECTED]> Date: Fri, 25 Feb 2005 13:56:33 -0500 Subject: Re: Calling C/C++ library routines To: MrJoltCola <[EMAIL PROTECTED]> On Fri, 25 Feb 2005 13:40:15 -0500, MrJoltCola <[EMAIL PROTECTED]> wrote: > At 01:27 PM 2/25/2005,

Re: Calling C/C++ library routines

2005-02-25 Thread Will Coleda
http://cvs.perl.org/viewcvs/cvs-public/parrot/examples/pni/ has examples for QT, sdl, and the win32 API. Regards. vlad florentino writes: Wow, that's great! Are there any examples showing how one can call C routines in Parrot? $vlad.f()

Re: Calling C/C++ library routines

2005-02-25 Thread chromatic
On Fri, 2005-02-25 at 14:18 -0500, Will Coleda wrote: > http://cvs.perl.org/viewcvs/cvs-public/parrot/examples/pni/ > > has examples for QT, sdl, and the win32 API. The actual NCI stuff (for SDL bindings, at least) is in: http://cvs.perl.org/viewcvs/cvs-public/parrot/runtime/parrot/library/

RE: [perl #34258] [TODO] Here documents for PIR

2005-02-25 Thread Garrett Goebel
Melvin wrote: > > Parrot need's its own version of "C" or "C#" to empower more people > to contribute. If every new feature for Parrot is thought of in > terms of PIR & IMCC, then IMCC will just become more of a tangled > mess that nobody wants to touch, and high-level development will > continue

Re: [RESENT] (was: [perl #32989] Problem in linux ppc)

2005-02-25 Thread chromatic
On Fri, 2005-02-25 at 12:31 +0100, Leopold Toetsch wrote: > I'm still waiting for confirmation that the recipe below works for > ppc-linux. Nope, the assembler here doesn't understand the code. Here's what worked for me. -- c #define PPC_JIT_GP_REGISTER_SAVE_SPACE (4*19) ;; This macro would

[ANN] Pugs Apocryphon 1: Overview of the Pugs project

2005-02-25 Thread Autrijus Tang
Greetings. Sorry for the cross-posting; the subsequent Apocrypha installments will appear on perl6-compiler only. But since this one deal with the relationship between Pugs and the existing Perl5/Perl6 projects, I thought it may help to cross-post this announcement. The full text of PA01 is avai

Re: [RESENT] (was: [perl #32989] Problem in linux ppc)

2005-02-25 Thread chromatic
On Fri, 2005-02-25 at 13:18 -0800, chromatic wrote: > Nope, the assembler here doesn't understand the code. Here's what > worked for me. Ignore that attachment, it's wrong. Here's the right one. -- c .text .align 12 .globl Parrot_ppc_jit_restore_nonvolatile_reg

Re: Q: about Parrot assembly code

2005-02-25 Thread Steve Coleman
MrJoltCola wrote: I doubt there is much that could not be mapped to Parrot, but Parrot does things that would be impossible to map directly back to a CPU. Currently I am only thinking of just a CPU X to Parrot asm translation, not the reverse, and this is just an attempt to get to a consolidated

Re: TAP and STDERR

2005-02-25 Thread Michael G Schwern
On Fri, Feb 25, 2005 at 10:22:33AM -0500, Joe Schaefer wrote: > > More to the point is its completely unstructured output that comes not > > as part of the test but between them. > > It might be worthwhile to associate that "unstructured output" with > a particular test (either the previous "ok/n