Re: summer of code mentor applications starting (and ending) next week

[Eric Wilhelm]

# from Nicholas Clark
# on Friday 29 February 2008 06:58:

>There is no such thing as a p5p admin*.

No, it would need to be somebody on behalf of TPF, as google needs 
somewhere to send the mentorship check.

Alternatively, a company or individual attached to a sufficiently large 
perl-based project could submit their application separately (at least 
Catalyst, mod_perl, and RT come to mind.)  But for hacking 

The only requirement is that you be an entity with which google (a US 
organization) can legally do business (and of course: that you 
represent a vibrant open source project.)

I'm told that the TPF website is out-of-date.  Richard?  We need to 
start building a list of mentors, but they need someone at TPF to 
contact.

>>>   http://code.google.com/soc/2008/

>>>  "The organization should choose a single administrator to submit
>>>  its application via the GSoC web app between March 3-12, 2008."

--Eric
-- 
The opinions expressed in this e-mail were randomly generated by
the computer and do not necessarily reflect the views of its owner.
--Management
---
http://scratchcomputing.com
---

Re: Eclipse

[Ron Blaschke]

Andy Lester wrote:
Anyone out there using Eclipse?  I figure there might be value in its 
ability to handle large codebases all at once.


Any pointers for startup and using the existing parrot project?


I know Eclipse a bit from Java development.  You'd probably want to 
start with "Eclipse IDE for C/C++ Developers" or "Eclipse Classic" from 
.  If I got this right, all packages 
contain the core platform and a set of default plugins, though you can 
always change your mind what plugins you want later on.  I usually start 
out with "Eclipse Classic."  C/C++ support lives in the CDT plugin 
.  See also 



For Subversion integration I use Subclipse 
.  For Perl there's EPIC 
, though I have never used it.  Plugins 
can be installed by opening Help -> Software Updates, adding the Update 
URL as Remote Site and select the plugins you want.


Eclipse projects live in a workspace, which also contains all settings. 
 I usually just create a workspace directory in my home directory and 
make Eclipse use it by default.  You can change your mind with File -> 
Switch Workspace or the "-data " option on the command line.  Maybe 
you want a separate Parrot workspace for all Parrot related projects.


Add the project with File -> New -> Project.  Give it a name and select 
your Parrot directory as Location.


Workspaces are usually rebuild on change, but you can stop this by 
unchecking Project -> Build Automatically.


The project settings are stored in .project and .settings in the project 
directory.


That's all I can think of right now.

Ron

[perl #51290] [BUG]: Failures in t/compilers/imcc/syn/errors.t and macro.t

[via RT]

# New Ticket Created by  James Keenan 
# Please include the string:  [perl #51290]
# in the subject line of all future correspondence about this issue. 
# http://rt.perl.org/rt3/Ticket/Display.html?id=51290 >


Failures observed on:  Linux:  Debian-stable.
At revision 26137.

[li11-226:parrot] 507 $ prove -v t/compilers/imcc/syn/errors.t 
t/compilers/imcc/syn/macro.t
t/compilers/imcc/syn/errors..
1..5
ok 1 - op not found.
ok 2 - check parser recovery 1.
ok 3 - check parser recovery patience.
ok 4 - SomethingFunny isnt pmc
not ok 5 - Array isnt pmc

#   Failed test 'Array isnt pmc'
#   at lib/Parrot/Test.pm line 713.
# Expected error but exited cleanly
# Received:
# hello
#
# Expected:
# /^error:imcc:Unknown PMC type 'Array'/
#
# Looks like you failed 1 test of 5.
 Dubious, test returned 1 (wstat 256, 0x100)
 Failed 1/5 subtests
t/compilers/imcc/syn/macro...
1..34
ok 1 - macro, zero parameters
ok 2 - macro, one unused parameter, literal term
ok 3 - macro, one unused parameter, register term
ok 4 - macro, one used parameter, literal
ok 5 - macro, one used parameter, register
ok 6 - macro, one used parameter, called twice
ok 7 - macro, one used parameter, label
ok 8 - macro, one used parameter run thrice, label
ok 9 - constant defined and used
ok 10 - constant defined and used
ok 11 - constant defined, used in a macro call
ok 12 - basic include macro
ok 13 - include a file defining a macro
ok 14 - .newid
ok 15 - .newlex
ok 16 - too few params
ok 17 - too many params
ok 18 - ok param count
ok 19 - macro name is no ident
ok 20 - unterminated macro
ok 21 - unterminated macro 2
ok 22 - ill param def
ok 23 - no params
ok 24 - unknown macro
ok 25 - unexpected IDENTIFIER
ok 26 - unknown macro
ok 27 - braces in param
ok 28 - braces and comma, with a newline in param
ok 29 - braces and parenthesis in param
ok 30 - test that macros labels names can have the prefix $
ok 31 - test that macros labels names can have the prefix $
not ok 32 - invalid label syntax (RT\#47978, RT\#51104)

#   Failed test 'invalid label syntax (RT\#47978, RT\#51104)'
#   at t/compilers/imcc/syn/macro.t line 438.
#   'compilers/imcc/imcc.l:994: failed assertion 'valp->s'
# Backtrace - Obtained 11 stack frames (max trace depth is 32).
#   (unknown)
# Parrot_confess
#   Parrot_assert
# (unknown)
#   yylex
# yyparse
#   (unknown)
# imcc_run
#   (unknown)
# __libc_start_main
#   (unknown)
# '
# doesn't match '/syntax error, unexpected LABEL/
# '
# './parrot   "/home/jimk/work/parrot/t/compilers/imcc/syn/macro_32.pir"' 
failed with exit code [SIGNAL 6]
ok 33 - call a sub in a macro
ok 34 - set a sub as an attribute, in a macro
# Looks like you failed 1 test of 34.
 Dubious, test returned 1 (wstat 256, 0x100)
 Failed 1/34 subtests

Test Summary Report
---
t/compilers/imcc/syn/errors.t (Wstat: 256 Tests: 5 Failed: 1)
  Failed test:  5
  Non-zero exit status: 1
t/compilers/imcc/syn/macro.t (Wstat: 256 Tests: 34 Failed: 1)
  Failed test:  32
  Non-zero exit status: 1
Files=2, Tests=39,  4 wallclock secs ( 0.01 usr  0.00 sys +  0.48 cusr  0.11 
csys =  0.60 CPU)
Result: FAIL

Re: [svn:parrot] r26138 - trunk/src

[chromatic]

On Friday 29 February 2008 16:21:16 [EMAIL PROTECTED] wrote:

> Modified:
>trunk/src/hll.c
>trunk/src/key.c
>
> Log:
> Applying two documentation patches submitted by Alan Rocker. ajr++
>
>
> Modified: trunk/src/hll.c
> ===
>=== --- trunk/src/hll.c(original)
> +++ trunk/src/hll.c   Fri Feb 29 16:21:15 2008
> @@ -62,7 +62,10 @@
>
>  =item C
>
> -RT#48260: Not yet documented!!!
> +Create a new HLL information table entry.
> +Takes an interpreter name and (optional) entry name.

Nit: interpreters don't have names.

-- c

[perl #51290] [BUG]: Failures in t/compilers/imcc/syn/errors.t and macro.t

[James Keenan via RT]

On Fri Feb 29 15:31:39 2008, [EMAIL PROTECTED] wrote:

> 
> This problem is fixed by the patch I've attached to ticket #51280.


Applied that patch to my sandbox.  It fixed the problem with error.t but
not the one with macro.t:

[li11-226:parrot] 512 $ prove -v t/compilers/imcc/syn/macro.t
t/compilers/imcc/syn/macro..
1..34

[snip]

ok 31 - test that macros labels names can have the prefix $
not ok 32 - invalid label syntax (RT\#47978, RT\#51104)

#   Failed test 'invalid label syntax (RT\#47978, RT\#51104)'
#   at t/compilers/imcc/syn/macro.t line 438.
#   'compilers/imcc/imcc.l:994: failed assertion 'valp->s'
# Backtrace - Obtained 11 stack frames (max trace depth is 32).
#   (unknown)
# Parrot_confess
#   Parrot_assert
# (unknown)
#   yylex
# yyparse
#   (unknown)
# imcc_run
#   (unknown)
# __libc_start_main
#   (unknown)
# '
# doesn't match '/syntax error, unexpected LABEL/
# '
# './parrot  
"/home/jimk/work/parrot/t/compilers/imcc/syn/macro_32.pir"' failed with
exit code [SIGNAL 6]
ok 33 - call a sub in a macro
ok 34 - set a sub as an attribute, in a macro
# Looks like you failed 1 test of 34.
 Dubious, test returned 1 (wstat 256, 0x100)
 Failed 1/34 subtests 

Test Summary Report
---
t/compilers/imcc/syn/macro.t (Wstat: 256 Tests: 34 Failed: 1)
  Failed test:  32
  Non-zero exit status: 1
Files=1, Tests=34,  3 wallclock secs ( 0.01 usr  0.00 sys +  0.45 cusr 
0.12 csys =  0.58 CPU)
Result: FAIL

[perl #51290] [BUG]: Failures in t/compilers/imcc/syn/errors.t and macro.t

[James Keenan via RT]

Got similar output for continuing failure on macro.t on Darwin:

t/compilers/imcc/syn/macro.
#   Failed test 'invalid label syntax (RT\#47978, RT\#51104)'
#   at t/compilers/imcc/syn/macro.t line 438.
#   'compilers/imcc/imcc.l:994: failed assertion 'valp->s'
# '
# doesn't match '/syntax error, unexpected LABEL/
# '
# './parrot -D40 --gc-debug 
"/Users/jimk/work/parrot/t/compilers/imcc/syn/macro_32.pir"' failed with
exit code [SIGNAL 6]
# Looks like you failed 1 test of 34.
 Dubious, test returned 1 (wstat 256, 0x100)
 Failed 1/34 subtests 

[perl #51170] [PATCH] Use rm -f instead of rm -rf to remove files

[James Keenan via RT]

No one objected.  I re-tested on Darwin, with satisfactory results. 
Applied to trunk in r26140.

[perl #51290] [BUG]: Failures in t/compilers/imcc/syn/errors.t and macro.t

[James Keenan via RT]

Reviewing the RT queue, I see that t/compilers/imcc/syn/macro.t is the
subject of an earlier ticket, # 50920.  So I am going to merge this
ticket into that one.

kid51

[perl #38262] [CAGE] get external Perl5 modules out of the parrot repo

[James Keenan via RT]

On Wed Feb 27 09:40:57 2008, [EMAIL PROTECTED] wrote:

> 
> Two possible solutions:  Either eliminate those 6 tests entirely, or
> rewrite the tests to make the regexes which need to be matched tolerant
> of the differences between Test::Builder 0.60 and 0.72 in this regard.
> 

Like chromatic, I am leaning toward making the regexes more tolerant. 
Unfortunately, that will only remedy the situation in 2 of the 6 cases
-- because the other 4 tests are for exact matches:

515 $ grep -n failure t/perl/Parrot_Test.t 
102:$desc = 'pasm_output_is: failure';
133:$desc = 'pasm_output_isnt: failure';
165:$desc = 'pasm_output_like: failure';
198:$desc = 'pir_output_is: failure';
231:$desc = 'pir_output_isnt: failure';
265:$desc = 'pir_output_like: failure';

Can someone suggest some suitable unit tests for the '_is' and '_isnt'
cases?

kid51

Re: Perl 6 fundraising and related topics.

[Dave Rolsky]

On Tue, 26 Feb 2008, Ovid wrote:


How else should we be advertising this?


These mailing lists might be a good place. Basically, places where the 
work in question is done also seem like good places to advertise.



-dave

/*===
VegGuide.Orgwww.BookIRead.com
Your guide to all that's veg.   My book blog
===*/