On Feb 2, 2006, at 2:33, Allison Randal (via RT) wrote:
I've spent too much time on this error, so I'm routing around it, but
I'd love to figure out what's causing it. In my local version of
Punie I get this error when I run 'make test':
[ ... ]
... Also, if I modify the Punie compiler to d
On Wednesday 01 February 2006 09:10 am, Audrey Tang wrote:
> Beau E. Cox wrote:
> > Compiled/intstalled parrot-0.4.1 revision 11397 (svn). OK.
> > Downloaded pugs 6.2.11 revision 8909 (svn).
>
> r8927 added a probe to Makefile.PL: According to Leo, you need to keep
> the original Parrot source tree
Adam Kennedy <[EMAIL PROTECTED]> wrote:
> Write this up. Then exhaustively test it on every single Perl platform
> (50ish?) and every Perl version back to 5.004, including a random
> collection similarly weird combinations (5.004 VMS, "that" 5.6.0 from
> RedHat 7, 5.6.1 on Windows 95).
The the darwin hints and MANIFEST.generated changes look OK but the
root.in changes will review some more review.
As a side note it's pretty clear that MANIFEST.generated needs to be
machine generated itself.
-J
--
On Wed, Feb 01, 2006 at 04:53:46PM -0800, Joshua Isom wrote:
> # New Ticket Creat
Hi -
Congrats on your 6.2.11 release!
Did the development (svn) version really jump to 6.28.0?
I am running some scripts to automate a refresh of parrot and
pugs weekly so I can stay in tune with the current effort.
To identify my svn downloads by version and revision I:
1) slurp ChangeLog and
Leopold Toetsch wrote:
But C statics can of course change. The problems is, where to
store the static variable, especially native integers.
Another idea:
We keep the call frame of subs with statics (or Perl6 INIT and FIRST
blocks) after returning from the sub. Additionally, we can set a new
On Thu, Feb 02, 2006 at 02:56:09AM -0800, Tyler MacDonald wrote:
> A new module doesn't need to be added to the core, so long as there
> is a way that we can reliably detect when a person wishes to build and test
> any given perl package for an objectively unselfish purpose such as
> 1:prepac
Hi,
Tyler MacDonald wrote:
And now that I think about it, I'm not so convinced about that whole
"concenience for the end user" nonsense. If they're mucking about installing
perl modules from the CPAN packages by themself, they're probably developers
that need some extra time to sit there
On Feb 1, 2006, at 10:35 PM, Tyler MacDonald wrote:
Chris Dolan <[EMAIL PROTECTED]> wrote:
There is a class of tests that module authors perform that end users
are not expected to run. For example code coverage tests, spelling
tests, coding style tests, etc. These tests are either prohibitive
On Thu, Feb 02, 2006 at 12:51:36PM +0100, Leopold Toetsch wrote:
: Another idea:
:
: We keep the call frame of subs with statics (or Perl6 INIT and FIRST
: blocks) after returning from the sub. Additionally, we can set a new
: entrypoint for the sub after running the INIT code (or static
: init
On Thu, Feb 02, 2006 at 11:33:25AM +0100, Leopold Toetsch wrote:
:
: On Feb 2, 2006, at 2:33, Allison Randal (via RT) wrote:
:
: >I've spent too much time on this error, so I'm routing around it, but
: >I'd love to figure out what's causing it. In my local version of
: >Punie I get this error whe
Steffen Mueller <[EMAIL PROTECTED]> wrote:
> > And now that I think about it, I'm not so convinced about that whole
> >"concenience for the end user" nonsense. If they're mucking about
> >installing perl modules from the CPAN packages by themself, they're
> >probably developers that need some e
* Chris Dolan <[EMAIL PROTECTED]> [2006-02-02 16:55]:
>On Feb 1, 2006, at 10:35 PM, Tyler MacDonald wrote:
>>I really like this idea. But as you pointed out, it's not just
>>authors that need to worry about running these tests, it's
>>packagers (ppm/deb/etc), automated testers
>>(cpants/testers.cpa
Larry Wall wrote:
On Thu, Feb 02, 2006 at 12:51:36PM +0100, Leopold Toetsch wrote:
: Another idea:
:
: We keep the call frame of subs with statics (or Perl6 INIT and FIRST
: blocks) after returning from the sub. Additionally, we can set a new
: entrypoint for the sub after running the INIT cod
Chris Dolan <[EMAIL PROTECTED]> wrote:
> * copyright.t - Ensures that there is a "Copyright ".([localtime]->
> [5]+1900) somewhere in every .pm file. Will break 11 months from now.
> * distribution.t - Relies on Test::Distribution, which is not in my
> prereq list
> * perlcritic.t - Runs Tes
A. Pagaltzis <[EMAIL PROTECTED]> wrote:
> I was just gonna say. It???s pointless for anyone but the author to
> check POD or test coverage.
I agree about the POD coverage. But if I got a different level of
code coverage on somebody else's system than my own? I'd be very interested
in findi
A. Pagaltzis wrote:
> * Chris Dolan <[EMAIL PROTECTED]> [2006-02-02 16:55]:
>> On Feb 1, 2006, at 10:35 PM, Tyler MacDonald wrote:
>>> I really like this idea. But as you pointed out, it's not just
>>> authors that need to worry about running these tests, it's
>>> packagers (ppm/deb/etc), automated
On Thursday 02 February 2006 10:04, Tyler MacDonald wrote:
> A. Pagaltzis <[EMAIL PROTECTED]> wrote:
> > I was just gonna say. It???s pointless for anyone but the author to
> > check POD or test coverage.
> I agree about the POD coverage. But if I got a different level of
> code coverage o
On Thursday 02 February 2006 02:56, Tyler MacDonald wrote:
> And now that I think about it, I'm not so convinced about that whole
> "concenience for the end user" nonsense. If they're mucking about
> installing perl modules from the CPAN packages by themself, they're
> probably developers th
Hmm,
There are sevral appears in S05 which use => instead of -> in a for loop.
So, Is this a typo?
eg:
for @{$} => $pair {
say "Key: $pair[0]";
say "Val: $pair[1]";
}
Thanks,
Xinming
On Fri, Feb 03, 2006 at 03:02:12AM +0800, Yiyi Hu wrote:
: Hmm,
: There are sevral appears in S05 which use => instead of -> in a for loop.
: So, Is this a typo?
: eg:
: for @{$} => $pair {
: say "Key: $pair[0]";
: say "Val: $pair[1]";
: }
Yes, that's a typo. Thanks. It i
On Thu, Feb 02, 2006 at 11:33:25AM +0100, Leopold Toetsch wrote:
> On Feb 2, 2006, at 2:33, Allison Randal (via RT) wrote:
>
> >I've spent too much time on this error, so I'm routing around it, but
> >I'd love to figure out what's causing it. In my local version of
> >Punie I get this error when I
On 2/2/06, Patrick R. Michaud <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 02, 2006 at 11:33:25AM +0100, Leopold Toetsch wrote:
> > On Feb 2, 2006, at 2:33, Allison Randal (via RT) wrote:
> >
> > >I've spent too much time on this error, so I'm routing around it, but
> > >I'd love to figure out what's c
Patrick R. Michaud wrote:
This may or may not be related, but I'm getting a segfault for
building PGE itself (x86_64/linux), when trying to run mklib.pir
to generate the built-in rules.
Yep. Working on that currently. I've simplied it to this testcase now:
.sub main :method
.local int a
On Thu, Feb 02, 2006 at 01:32:49PM -0800, jerry gay wrote:
> > This may or may not be related, but I'm getting a segfault for
> > building PGE itself (x86_64/linux), when trying to run mklib.pir
> > to generate the built-in rules.
> >
> i'm getting this, too, on win32. as are others, i think, on ma
On Thu, Feb 02, 2006 at 07:12:08PM +0100, Leopold Toetsch wrote:
: >... Anyway,
: >the P6 model of "state" is more like a persistent lexical than like
: >C's static.
:
: Sorry for my dumb question - what's the difference then? (Besides that C
: dosn't have closures ;)
That *is* the difference.
Leopold Toetsch wrote:
.sub main :method
.local int a
(a,$S0) = self."foo"()
self."bar"()
.end
and
> ... get_results PMC_C[236] (5), I3, I0, I4, I1, S-1
This is solved now with r11408 / r11409.
leo
* Christopher H. Laco <[EMAIL PROTECTED]> [2006-02-02 18:50]:
>On more than one occasion, I've had pod2html/man (troff) errors
>under FreeBSD that were only found by running the author tests
>there, even though the pod syntax/coverage was perfectly fine on
>two other platforms.
Are you sure that’s
On Wed, Feb 01, 2006 at 05:33:29PM -0800, Allison Randal wrote:
> # New Ticket Created by Allison Randal
> # Please include the string: [perl #38406]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/rt3/Ticket/Display.html?id=38406 >
>
>
> I've sp
On Sun, Jan 29, 2006 at 08:13:44PM +, Luke Palmer wrote:
: On 1/29/06, Yuval Kogman <[EMAIL PROTECTED]> wrote:
: > Aside from that they are normal perl 6 subroutines, that simply get
: > invoked during compile time instead of during runtime.
:
: With one extra "feature". By default (my prefer
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t/rules/from_perl6_rules/array_ca 18 460845 10 22.22% 41-45
t/rules/from_perl6_rules/named_ca 18 460826 48 184.62% 3-2
After a little more cleanup, S06 now reads:
=head2 Macros
Macros are functions or operators that are called by the compiler as
soon as their arguments are parsed (if not sooner). The syntactic
effect of a macro declaration or importation is always lexically
scoped, even if th
* copyright.t - Ensures that there is a "Copyright
".([localtime]->[5]+1900) somewhere in every .pm file. Will break 11
months from now.
* distribution.t - Relies on Test::Distribution, which is not in my
prereq list
snipped ones that need your personal files, you are certainly right
there
chromatic wrote:
On Thursday 02 February 2006 10:04, Tyler MacDonald wrote:
A. Pagaltzis <[EMAIL PROTECTED]> wrote:
I was just gonna say. It???s pointless for anyone but the author to
check POD or test coverage.
I agree about the POD coverage. But if I got a different level of
cod
On Thursday 02 February 2006 17:45, Adam Kennedy wrote:
> Just as a datapoint on this topic, the PITA request objects (as of 5
> minutes ago) now support the ability to explicitly set environment
> variables you want set when running the tests, on top of the
> default-but-overridable ones like AU
* Adam Kennedy <[EMAIL PROTECTED]> [2006-02-03 02:45]:
>But I don't know that I like disttest autodetection. I quite
>like being able to run the additional tests manually if needed,
>and not be limited to only during the disttest process.
Maybe do it the other way around? Define INSTALL_AUTOMATED
On Thu, Feb 02, 2006 at 10:01:48AM -0800, Tyler MacDonald wrote:
I strongly feel that authors should keep everything necessary
for their distribution public; either in the CPAN distribution
itself, or via a "permanent" publicly available version control
system.
Who's to say you won't lose interes
> "LW" == Larry Wall <[EMAIL PROTECTED]> writes:
LW> pugs -V:
LW> This is Perl6 User's Golfing System, version 6.2.11, February 1,
LW> 2005 (r8945) built for i386-linux-thread-multi
not that this has anything to do with the bug(s) under question but i
see a y2k+5 bug right t
On Thu, Feb 02, 2006 at 10:58:39PM -0500, Uri Guttman wrote:
: > "LW" == Larry Wall <[EMAIL PROTECTED]> writes:
:
: LW> pugs -V:
:
: LW> This is Perl6 User's Golfing System, version 6.2.11, February 1,
: LW> 2005 (r8945) built for i386-linux-thread-multi
:
:
: not that this
That doesn't allow for what happens if both are missing.
I find the following a good general rule.
There are tests that test how the code actually works, that could
convievably be different on different platforms.
These are always on.
There are tests for issues that are almost certainly (but
On Feb 2, 2006, at 9:19 PM, Yitzchak Scott-Thoennes wrote:
Chris, how are you currently set up to run these tests only when
preparing a release?
I make no such distinction. Instead, I see these tests as part of my
day-to-day development and run all of them with every "./Build
test". Pres
> "LW" == Larry Wall <[EMAIL PROTECTED]> writes:
LW> On Thu, Feb 02, 2006 at 10:58:39PM -0500, Uri Guttman wrote:
LW> :
LW> : LW> This is Perl6 User's Golfing System, version 6.2.11, February 1,
LW> : LW> 2005 (r8945) built for i386-linux-thread-multi
LW> :
LW> :
(from p6i)
Larry Wall wrote:
On Thu, Feb 02, 2006 at 07:12:08PM +0100, Leopold Toetsch wrote:
: >... Anyway,
: >the P6 model of "state" is more like a persistent lexical than like
: >C's static.
:
: Sorry for my dumb question - what's the difference then? (Besides that C
: dosn't have closur
Hi -
When making pugs, I know that the following env must be
setup to imbed parrot:
...
export PUGS_EMBED="perl5 parrot"
export PARROT_PATH="/the/parrot/built/source/tree"
...
Is the parrot source tree only needed for the pugs make?
Can I get rid of it after pugs is sucessfully installed?
Is thi
On 2/3/06, Dave Whipp <[EMAIL PROTECTED]> wrote:
>sub factorial(Int $x) {
>temp state Int $result = 1;
>$result *= $x;
>factorial $x-1 if $x > 2;
>return $result if want;
>}
>say factorial 6;
That's precisely what "env" variables are for. The right way:
On Thursday 02 February 2006 05:55 pm, Kevin Puetz wrote:
> Beau E. Cox wrote:
> > Hi -
> >
> > Congrats on your 6.2.11 release!
> >
> > Did the development (svn) version really jump to 6.28.0?
>
> Yes. Major pugs releases are numbered by adding the next digit of 2*pi,
> rather than the more conven
46 matches
Mail list logo
