Re: Bytecode portability and word/int sizes

2003-11-23 Thread Leopold Toetsch
Melvin Smith [EMAIL PROTECTED] wrote: At 11:34 PM 11/22/2003 +0100, Leopold Toetsch wrote: The concept of having INTVAL constants inside the opcodes is wrong from a general POV. Please have a look at e.g jit/arm/ what immediate constants are requiring as work arounds. I'm not aware of those

Re: Some PIR How do I? questions

2003-11-23 Thread Gregor N. Purdy
Umm.. Do you mean: package Foo::Bar; sub new { my $class = shift; return bless { jo = 42 }, $class; } sub prnJoe { my $self = shift; print $self-{jo}, \n; } package main; $f = Foo::Bar-new(); $f-prnJoe();

Re: Bytecode portability and word/int sizes

2003-11-23 Thread Melvin Smith
At 01:07 PM 11/23/2003 +0100, Leopold Toetsch wrote: Melvin Smith [EMAIL PROTECTED] wrote: At 11:34 PM 11/22/2003 +0100, Leopold Toetsch wrote: Ix regs are for: 1) Fast integer stuff 2) Iteration (increment variables) 3) Conditional checks 4) Branching and holding addresses 5) Indexing

'catch' statement modifier

2003-11-23 Thread Luke Palmer
I was reading over some code that used the MIDI module, and saw the Cwrite_to_file method. I began wondering, how does one report the error if he feels like it, but let the module report the error if not, in a concise way. What about something along the lines of a Ccatch statement modifier,

Re: 'catch' statement modifier

2003-11-23 Thread Tony Olekshy
Luke ~ These matters are covered at some length in RFC 88 and Apocalypse 4. http://www.avrasoft.com/perl6/rfc88.htm http://www.perl.com/pub/a/2002/01/15/apo4.html Yours, c, Tony Olekshy Luke Palmer wrote, at 2003-11-23 11:55: I was reading over some code that used the MIDI module,

Re: 'catch' statement modifier

2003-11-23 Thread Damian Conway
I was reading over some code that used the MIDI module, and saw the Cwrite_to_file method. I began wondering, how does one report the error if he feels like it, but let the module report the error if not, in a concise way. What about something along the lines of a Ccatch statement modifier, like:

RE: 'catch' statement modifier

2003-11-23 Thread Austin Hastings
-Original Message- From: Damian Conway [mailto:[EMAIL PROTECTED] Remember that a Ctry without a CCATCH catches all exceptions and returns Cundef (the same as a Perl 5 Ceval block does). So you just want: try { $opus.write_to_file($file) } err die

Re: 'catch' statement modifier

2003-11-23 Thread Damian Conway
Austin Hastings wrote: try { $opus.write_to_file($file) } err die Couldn't write to $file: $!\n; Is that Cerr die or Cor die ? It's Cerr, which is low precedence C//. And if so, what's Cerr and where can I find more on it?

Re: 'catch' statement modifier

2003-11-23 Thread Damian Conway
Hmm. I think I may have missed Luke's point. Which was (presumably): what if C$opus.write_to_file($file); validly returns Cundef? In which case I think we just fall back to: try{$opus.write_to_file($file); CATCH {die Couldn't write to $file: $!}} which is, after all, only 5 characters

Re: 'catch' statement modifier

2003-11-23 Thread Jonathan Scott Duff
On Sun, Nov 23, 2003 at 03:53:00PM -0500, Austin Hastings wrote: -Original Message- From: Damian Conway [mailto:[EMAIL PROTECTED] Remember that a Ctry without a CCATCH catches all exceptions and returns Cundef (the same as a Perl 5 Ceval block does). So you just want:

Win32 building

2003-11-23 Thread Vladimir Lipsky
D:\build\parrotnmake ... d:\build\parrot\src\encoding.c(39) : warning C4090: 'function' : different 'const' qualifiers d:\build\parrot\src\encoding.c(39) : warning C4022: 'mem_sys_free' : pointer mismatch for actual parameter 1 ... d:\build\parrot\src\chartype.c(231) : warning C4090: 'function' :