[svn:parrot-pdd] r12202 - trunk/docs/pdds/clip
Author: coke Date: Thu Apr 13 13:51:48 2006 New Revision: 12202 Modified: trunk/docs/pdds/clip/pddXX_exceptions.pod Log: Fix bug in PDD exception handling example. Modified: trunk/docs/pdds/clip/pddXX_exceptions.pod == --- trunk/docs/pdds/clip/pddXX_exceptions.pod (original) +++ trunk/docs/pdds/clip/pddXX_exceptions.pod Thu Apr 13 13:51:48 2006 @@ -256,7 +256,7 @@ ... _handler: # if not, execution continues here -get_params '(0,0)', P0, S0 # handler is called with (exception, message) +get_results '(0,0)', P0, S0 # handler is called with (exception, message) ... If the global variable is found, the next statement
[perl #38914] perl Configure.pl fails on Mac OS X 10.4.6 on Intel iMac
# New Ticket Created by Gregor N. Purdy
# Please include the string: [perl #38914]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38914 >
$ perl Configure.pl
Parrot Version 0.4.3 Configure 2.0
Copyright (C) 2001-2006 The Perl Foundation. All Rights Reserved.
Hello, I'm Configure. My job is to poke and prod your system to
figure out
how to build Parrot. The process is completely automated, unless you
passed in
the `--ask' flag on the command line, in which case it'll prompt you
for a few
pieces of info.
Since you're running this script, you obviously have Perl 5--I'll be
pulling
some defaults from its configuration.
Checking
MANIFEST.done.
Setting up Configure's default
values.done.
Tweaking settings for
miniparrot...skipped.
Loading platform and local hints
filesdone.
Determining nongenerated header
files.done.
Determining what C compiler and linker to
use.done.
Determining whether make is
installed...no.
Determining whether lex is
installed...skipped.
Determining whether yacc is
installed..skipped.
Determining if your C compiler is actually gcc...
step auto::gcc died during execution: C compiler failed (see
test.cco) at lib/Parrot/Configure/Step.pm line 362
Parrot::Configure::Step::cc_build() called at config/auto/
gcc.pm line 36
auto::gcc::runstep('auto::gcc=HASH(0x8cde0)',
'Parrot::Configure=HASH(0x182bdc0)') called at lib/Parrot/
Configure.pm line 239
eval {...} called at lib/Parrot/Configure.pm line 235
Parrot::Configure::runsteps('Parrot::Configure=HASH
(0x182bdc0)') called at Configure.pl line 442
at Configure.pl line 442
r$ uname -a
Darwin Family.local 8.6.1 Darwin Kernel Version 8.6.1: Tue Mar 7
16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386 i386 i386
r$
[perl #38896] [TODO] Integer PMC missing math methods.
Note that there don't seem to be any tests, for example, against something like: $P1 = new .Float $P1 = 1.2 $N1 = cosh $P1 op/trans.t tests some of these math ops, but only against N registers. There are tests for the complex PMC, but not Float. Add tests for all math opcodes for Float & Integer. > [coke - Tue Apr 11 07:05:31 2006]: > > There are many math ops that work on Float PMCs but not Integer PMCs. > > e.g.: > % cat foo.pir > .sub main > > P1 = new .Float > P1 = 123 > P1 = exp P1 > print P1 > print "\n" > .end > % ./parrot foo.pir > Method 'exp' not found > current instr.: 'main' pc 12 (foo.pir:6) > > The assignment of 123 autoconverts the float to an integer, which > doesn't support the 'exp' method that's defined in the Float pmc. > (Change the 123 to 123. and it works fine.) > > Given the morphing that typically happens, I'd expect to be able to > do numeric (as opposed to integer) ops on integer pmcs and have it > autoconvert to float. > > exp is one of *many* math ops this needs to be done. Check out the > Methods POD section of src/pmc/float.pmc for the list. > >
@slash@ in Makefile.in Files
Looking at patch #12967, particle revised a previous patch and replace @slash@ with / in paths in the Makefile. I used the former out of a cargo-cult sense of platform independence. Is that unnecessary, or is it still a good idea? -- c
Re: @slash@ in Makefile.in Files
On 4/14/06, chromatic <[EMAIL PROTECTED]> wrote: > Looking at patch #12967, particle revised a previous patch and replace @slash@ > with / in paths in the Makefile. I used the former out of a cargo-cult sense > of platform independence. Is that unnecessary, or is it still a good idea? > config/gen/makefiles.pm offers a 'replace-slashes' option for makefiles, which does the right thing, and makes @slash@ unnecessary if it's specified.
Re: [perl #38914] perl Configure.pl fails on Mac OS X 10.4.6 on Intel iMac
What does
% gcc -v
say?
On Apr 13, 2006, at 10:32 PM, Gregor N.Purdy (via RT) wrote:
# New Ticket Created by Gregor N. Purdy
# Please include the string: [perl #38914]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=38914 >
$ perl Configure.pl
Parrot Version 0.4.3 Configure 2.0
Copyright (C) 2001-2006 The Perl Foundation. All Rights Reserved.
Hello, I'm Configure. My job is to poke and prod your system to
figure out
how to build Parrot. The process is completely automated, unless you
passed in
the `--ask' flag on the command line, in which case it'll prompt you
for a few
pieces of info.
Since you're running this script, you obviously have Perl 5--I'll be
pulling
some defaults from its configuration.
Checking
MANIFEST.done.
Setting up Configure's default
values.done.
Tweaking settings for
miniparrot...skipped.
Loading platform and local hints
filesdone.
Determining nongenerated header
files.done.
Determining what C compiler and linker to
use.done.
Determining whether make is
installed...no.
Determining whether lex is
installed...skipped.
Determining whether yacc is
installed..skipped.
Determining if your C compiler is actually gcc...
step auto::gcc died during execution: C compiler failed (see
test.cco) at lib/Parrot/Configure/Step.pm line 362
Parrot::Configure::Step::cc_build() called at config/auto/
gcc.pm line 36
auto::gcc::runstep('auto::gcc=HASH(0x8cde0)',
'Parrot::Configure=HASH(0x182bdc0)') called at lib/Parrot/
Configure.pm line 239
eval {...} called at lib/Parrot/Configure.pm line 235
Parrot::Configure::runsteps('Parrot::Configure=HASH
(0x182bdc0)') called at Configure.pl line 442
at Configure.pl line 442
r$ uname -a
Darwin Family.local 8.6.1 Darwin Kernel Version 8.6.1: Tue Mar 7
16:55:45 PST 2006; root:xnu-792.9.22.obj~1/RELEASE_I386 i386 i386
r$
Re: [perl #38914] perl Configure.pl fails on Mac OS X 10.4.6 on Intel iMac
On 4/13/06, via RT Gregor N. Purdy <[EMAIL PROTECTED]> wrote: > Determining if your C compiler is actually gcc... > step auto::gcc died during execution: C compiler failed (see > test.cco) at lib/Parrot/Configure/Step.pm line 362 what does test.cco say?
Re: @slash@ in Makefile.in Files
The makefile generator has an option to automatically do the slash replacement for you. In the interest of readability, I recommend using that and removing @slash@ from the .in files. (Do make sure if you change other .in files that they have this option enabled. Example from config/gen/makefiles.pm: genfile( 'config/gen/makefiles/root.in' => 'Makefile', commentType=> '#', replace_slashes=> 1, conditioned_lines => 1 ); On Apr 14, 2006, at 3:35 PM, chromatic wrote: Looking at patch #12967, particle revised a previous patch and replace @slash@ with / in paths in the Makefile. I used the former out of a cargo- cult sense of platform independence. Is that unnecessary, or is it still a good idea? -- c
