Re using perl.com articles in your Perl 6 wiki documentation, were you
also planning on adding (links to) Larry Wall's annual State of the
Onion talks? They contain a wealth of great language design
philosophy for people wanting to learn about what sorts of things
motivated the exceedingly
I'm having trouble with the initial Configure.pl and with the pbc_to_c
target on my Intel Macbook. I have rough notes below about the steps
I've taken. If anyone needs more information, just ask and I'd be
happy to send anything I can.
Following the instructions in chromatic's post at use.perl
Christian Mueller wrote:
i don't know the actually state in the discussion about multiline
comments, but i would propose an idea.. a combination of POD's = and the
traditional route char...
Perl 6 already has a robust system for multiline and embedded
comments, as described in S02 under
On 30/12/2007, Jonathan Lang [EMAIL PROTECTED] wrote:
The only wart
is that '#( ... )' cannot begin at the very start of a line; but it's
easy enough to get around that restriction - say, with some leading
whitespace.
Thanks for the reply - can you please what is the problem with having
it in
Ovid wrote:
I got this error on the latest version from svn:
parrot $ perl Configure.pl
Base class package Parrot::Configure::Compiler is empty.
(Perhaps you need to 'use' the module which defines that package
first.)
at lib/Parrot/Configure.pm line 44
I have the same problem,
--- Ovid [EMAIL PROTECTED] wrote:
On a related note, I received this error message:
Ack, some files were missing! I can't continue running
without everything here. Please try to find the above
files and then try running Configure again.
Configure.pl kept running yet the message
first of all thanks to Jonathan Scott Duff, you will be named in the
scribes section of the p6doc
documentation too and
to chromatic: i will name the authors normally like in POD and make a
link to perl.com/p6
section in the p6doc where sources of all docs are named.
Conrad Schneiker: about
Author: kjs
Date: Sun Dec 30 05:35:58 2007
New Revision: 24299
Modified:
trunk/docs/pdds/pdd27_multiple_dispatch.pod
Log:
[pdd27] add note about :invocant parameters must be contiguous. No explanation
yet.
Modified: trunk/docs/pdds/pdd27_multiple_dispatch.pod
Author: kjs
Date: Sun Dec 30 05:44:09 2007
New Revision: 24301
Modified:
trunk/docs/pdds/draft/pdd19_pir.pod
Log:
[pdd19] add reference to pdd27 for the :multi flag.
Modified: trunk/docs/pdds/draft/pdd19_pir.pod
==
Ovid wrote:
I'm having trouble with the initial Configure.pl and with the pbc_to_c
target on my Intel Macbook. I have rough notes below about the steps
I've taken. If anyone needs more information, just ask and I'd be
happy to send anything I can.
Following the instructions in chromatic's
--- James E Keenan [EMAIL PROTECTED] wrote:
Hi James,
Although it is not required for running chromatic's process, you
might wish to begin with:
perl Configure.pl --test
... to see that the configuration and build tools all work properly
before you say 'make'.
Thanks for that tip.
On Dec 30, 2007, at 10:04 AM, Ovid wrote:
--- James E Keenan [EMAIL PROTECTED] wrote:
Hi James,
Although it is not required for running chromatic's process, you
might wish to begin with:
perl Configure.pl --test
... to see that the configuration and build tools all work properly
Author: kjs
Date: Sun Dec 30 05:41:24 2007
New Revision: 24300
Modified:
trunk/docs/pdds/draft/pdd19_pir.pod
Log:
[pdd19] remove .emit and .eom from pdd19; the tokens are no longer allowed by
imcc. the parser-generated symbol EMIT is still there, as it is used to force
the parser in PASM
# New Ticket Created by James Keenan
# Please include the string: [perl #49224]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=49224
I am filing this ticket as a way of keeping track of some problems
with our
# New Ticket Created by Alberto Simoes
# Please include the string: [perl #49222]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=49222
Mac OS Tiger on PPC G4
Perl 5.10
Parrot Revision: 24263
[EMAIL PROTECTED]
Amir E. Aharoni wrote:
On 30/12/2007, Jonathan Lang [EMAIL PROTECTED] wrote:
The only wart
is that '#( ... )' cannot begin at the very start of a line; but it's
easy enough to get around that restriction - say, with some leading
whitespace.
Thanks for the reply - can you please what is
From: James Keenan (via RT) [EMAIL PROTECTED]
Date: Sun, 30 Dec 2007 07:35:08 -0800
# New Ticket Created by James Keenan
# Please include the string: [perl #49224]
# in the subject line of all future correspondence about this issue.
# URL:
I was unable to reproduce the failure on Mac 10.4.11 with Perl 5.10.
[fresh] 593 $ prove t/library/mime_base64.t
t/library/mime_base64ok
All tests successful.
Files=1, Tests=550, 9 wallclock secs ( 7.74 cusr + 0.52 csys = 8.26 CPU)
Perhaps
On Sun Dec 30 09:04:25 2007, rgrjr wrote:
Was that when the server was down a few days ago? Over the past few
days, I have seen several examples of the MERGE request failed ... 200
OK syndrome (which is particularly wierd) with Subversion client
version 1.3.0. But I wouldn't swear that
James Keenan via RT wrote:
Perhaps it is strictly a 10.5 problem???
I'm with Tiger (10.4)
Perl Configuration:
[EMAIL PROTECTED] ambs]$ perl -V
Summary of my perl5 (revision 5 version 10 subversion 0) configuration:
Platform:
osname=darwin, osvers=8.11.0, archname=darwin-2level
Could this be related to a TAP::Parser problem?
From: James Keenan via RT [EMAIL PROTECTED]
Date: Sun, 30 Dec 2007 09:11:06 -0800
I was unable to reproduce the failure on Mac 10.4.11 with Perl 5.10.
[fresh] 593 $ prove t/library/mime_base64.t
t/library/mime_base64ok
All tests
From: James Keenan via RT [EMAIL PROTECTED]
Date: Sun, 30 Dec 2007 09:13:24 -0800
No, I first began to notice this two weeks ago. And the most frequent
occurrences were last night, when the maintenance on the server was
presumably complete.
Come to think of it, I did three
James Keenan via RT wrote:
Could this be related to a TAP::Parser problem?
TAP::Parser 3.05,
Updated to Parrot revision 24317.
Same problem.
Some hints on how can I debug it?
--
Alberto Simões - Departamento de Informática - Universidade do Minho
Campus de Gualtar - 4710-057
From: James Keenan via RT [EMAIL PROTECTED]
Date: Sun, 30 Dec 2007 09:31:55 -0800
Could this be related to a TAP::Parser problem?
I don't think so; it's not emitting any debugging output at all.
Inserting a strategically-placed PDB_backtrace call shows that this
fails in line 27 of
On Dec 30, 2007 6:10 PM, Jonathan Lang wrote:
Short answer: the compiler has no way of knowing whether the
programmer wants an embedded comment or a line comment; so instead of
guessing, it requires the programmer to disambiguate.
[...snip...]
# if ($test)
# {
.say;
# } else
On Sunday 30 December 2007 09:31:55 James Keenan via RT wrote:
Could this be related to a TAP::Parser problem?
That seems unlikely to me; the assertion comes from the internals of Parrot.
More likely some sort of memory corruption.
Can someone seeing this do a binary search to see which
On Sunday 30 December 2007 08:15:26 James Keenan wrote:
Doing a fresh checkout from trunk at r24302, I was able to get perl6
up and running on Linux following chromatic's instructions on
use.perl.org (with one correction).
However, I was not so succesful on ppc-darwin. Here's the data:
On Sun Dec 30 10:01:18 2007, rgrjr wrote:
Come to think of it, I did three commits each on Monday and Tuesday, and
must have seen it then (either or both days).
-- Bob
Perhaps not; the problem is intermittent. But yesterday I was getting
it on
On Sunday 30 December 2007 10:02:53 Bob Rogers wrote:
I don't think so; it's not emitting any debugging output at all.
Inserting a strategically-placed PDB_backtrace call shows that this
fails in line 27 of t/library/mime_base64.t, which is:
load_bytecode 'compilers/json/JSON.pbc'
Whitespace is significant in many places. Even in some of the corners
of Perl 5. Perl 6 has a different set of rules, and it will take some
getting used to, but the rules are designed to let you do things as
naturally as possible.This, for instance, works fine:
my @values =
# (1,2,3) #
chromatic via RT wrote:
On Sunday 30 December 2007 10:02:53 Bob Rogers wrote:
I don't think so; it's not emitting any debugging output at all.
Inserting a strategically-placed PDB_backtrace call shows that this
fails in line 27 of t/library/mime_base64.t, which is:
load_bytecode
Erm, Realclean, and worked *shame*
chromatic via RT wrote:
On Sunday 30 December 2007 09:31:55 James Keenan via RT wrote:
Could this be related to a TAP::Parser problem?
That seems unlikely to me; the assertion comes from the internals of Parrot.
More likely some sort of memory
Offer Kaye wrote:
#( commenting out a large code section, yey for Perl6 multi-line comments...
if ($foo) {
print ...or not :(\n
}
) # this should have been the end of the embedded comment
...and since it wasn't, you probably should have chosen other brackets such as:
#[[
--- chromatic [EMAIL PROTECTED] wrote:
The problem is -o -o in the two lines of the pbc_to_exe rule in the
Makefile,
and I suspect that that's because you're linking against libparrot.a
not
libparrot.so. (Parrot::Embed failed for Tim Bunce for similar
reasons.)
I don't know the
Sorry if I've missed something recent that means that this is expected
behaviour but r24318 is hanging during make test on Mac OS 10.5.1 /
Intel.
The test log and pictures of the process probe are here:
http://hexten.net/junk/20071230-193600/
--
Andy Armstrong, Hexten
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #49226]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=49226
This may be a duplicate bug report. Attempting to use ./parrotbug
results
Thanks for the reply - can you please what is the problem with having
it in the beginning of the line?
Short answer: the compiler has no way of knowing whether the
programmer wants an embedded comment or a line comment; so instead of
guessing, it requires the programmer to disambiguate.
Is
Sorry if I've missed something recent that means that this is expected
behaviour but r24318 is hanging during make test on Mac OS 10.5.1 /
Intel.
The test log and pictures of the process probe are here:
http://hexten.net/junk/20071230-193600/
I also have a few test failures on Ubuntu PPC
running the example at http://svn.pugscode.org/pugs/examples/algorithms/hanoi.pl
parrot ~/downloads/parrot-0.5.1/languages/perl6/perl6.pbc hanoi.pl
I get..
Null PMC access in isa()
current instr.: 'parrot;Perl6Object;make_proto' pc 55 (src/gen_builtins.pir:76)
called from Sub
From 'make test':
t/dynpmc/foo.ok
1/9 skipped: various reasons
t/dynpmc/gdbmhashok
t/dynpmc/rationalok
1/8 skipped: various reasons
... and these have been the results for these tests for
On Dec 30, 2007 8:10 AM, Jonathan Lang [EMAIL PROTECTED] wrote:
Let's say that the programmer in question wants to comment out all but
the third line; so he prefixes everything else with '#':
#if ($test)
#{
.say;
#} else {
# .doit;
#}
What the writer _wants_ this to do is the
I got burned by this problem myself today. Fortunately, google had
archived this thread, so the solution was easy: (1) Edit the html to
replace the '0' revision number; (2) re-run smoke-server.pl; (3) upgrade
Subversion.
The test coverage is quite high
(http://thenceforward.net/parrot/coverage/configure-build/config-auto-aio-pm.html)
and I don't think I can push it much higher. So I'm resolving the ticket.
kid51
I committed the most recent correction to this step class back on Sept
11 but forgot to resolve the ticket. No one has had any complaints, so
I'm resolving it now.
kid51
Although larger issues about testing of Parrot configuration step
classes remain outstanding (and will for some time), they're being
tracked in other tickets. The immediate issue in this ticket seems
resolved, as this test has been passing in all smoke reports for some
time. So I'm closing the
Andy Armstrong wrote:
Sorry if I've missed something recent that means that this is expected
behaviour but r24318 is hanging during make test on Mac OS 10.5.1 / Intel.
The test log and pictures of the process probe are here:
http://hexten.net/junk/20071230-193600/
I also have a few test
The patch has been in head for more than a week now, with no complaints.
So I'm resolving the ticket.
kid51
From: chromatic [EMAIL PROTECTED]
Date: Sun, 30 Dec 2007 10:42:43 -0800
On Sunday 30 December 2007 10:02:53 Bob Rogers wrote:
I don't think so; it's not emitting any debugging output at all.
Inserting a strategically-placed PDB_backtrace call shows that this
fails in line 27
# New Ticket Created by Joseph Sadusk
# Please include the string: [perl #49236]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=49236
I just updated parrot to svn rev 24322 and attempted to do a clean
build. The
On Sunday 30 December 2007 12:14:04 Andy Armstrong wrote:
t/examples/shootout.t (Wstat: 2560 Tests: 20
Failed: 10)
Failed test number(s): 3, 6-11, 17-19
Non-zero exit status: 10
Files=533, Tests=10515, 1609 wallclock secs (25.43 usr 3.37 sys +
1310.02 cusr
51 matches
Mail list logo
