D:\build\parrot>nmake
...
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' :
On Sun, Nov 23, 2003 at 03:53:00PM -0500, Austin Hastings wrote:
> > -Original Message-
> > From: Damian Conway [mailto:[EMAIL PROTECTED]
> >
> > Remember that a C without a C catches all exceptions
> > and returns
> > C (the same as a Perl 5 C block does).
> >
> > So you just want:
> >
Hmm. I think I may have missed Luke's point. Which was (presumably):
what if C<$opus.write_to_file($file);> validly returns C?
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 long
Austin Hastings wrote:
try { $opus.write_to_file($file) }
err die "Couldn't write to $file: $!\n";
Is that C or C ?
It's C, which is low precedence C.
And if so, what's C and where can I find more on it?
http://dev.perl.org/perl6/exegesis/E04.html#Read_or_Die
Damian
> -Original Message-
> From: Damian Conway [mailto:[EMAIL PROTECTED]
>
> Remember that a C without a C catches all exceptions
> and returns
> C (the same as a Perl 5 C block does).
>
> So you just want:
>
> try { $opus.write_to_file($file) }
> err die "Couldn't writ
I was reading over some code that used the MIDI module, and saw the
C 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 C statement modifier,
like:
$opus.write_to
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
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) Index
I was reading over some code that used the MIDI module, and saw the
C 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 C statement modifier,
like:
$opus.write_
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();
--
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
11 matches
Mail list logo
