chromatic chromatic at wgz.org writes:
Bogus to me is cannot install a dependency because, for all I can tell, the
tester has a space somewhere in a directory name somewhere in the path to
Perl and the tester's operating system and command shell just can't cope with
this.
That's well
On 3/14/06, Adam Kennedy [EMAIL PROTECTED] wrote:
It's just that the reporting system has a very limited view of what
should be stamped green, and what should be stamped red.
I've never like such breakdowns. Even adding only one more state/color
can make it a lot easier to interpret a result
Even better would be adding two more states so that you can
distinguish between prereq-failure, build-failure, test-failure and
ok.
Well actually I tried to sit down the other day and work out how many
distinct types of success/failure events there might be, for use in PITA.
The number
Matt Diephouse (via RT) wrote:
$P0 = compreg PIR
.return $P0(code)
.end
[EMAIL PROTECTED]:~/parrot$ parrot test.pir
attempt to access code outside of current code segment
[EMAIL PROTECTED]:~/parrot$
This was the cause of some trouble recently for Partcl (although I
Chip Salzenberg wrote:
Audrey, I just committed the below to pdd03 because I think it'll work for
Pugs. What say?
Say sane. Thanks!
Audrey
signature.asc
Description: OpenPGP digital signature
On Tue, Mar 14, 2006 at 23:04:02 +1100, Adam Kennedy wrote:
Even better would be adding two more states so that you can
distinguish between prereq-failure, build-failure, test-failure and
ok.
Well actually I tried to sit down the other day and work out how many
distinct types of
On 3/14/06, Adam Kennedy [EMAIL PROTECTED] wrote:
Even better would be adding two more states so that you can
distinguish between prereq-failure, build-failure, test-failure and
ok.
Well actually I tried to sit down the other day and work out how many
distinct types of success/failure
Adam Kennedy wrote:
Part of the problem comes in defining bogus.
This is a red herring. Consider the original proposal:
If a tester sends in a 'updated' report (matching all the appropriate
criteria), then the update should overwrite/mask the original.
There is no need to define the criteria
Hey! It's been over two months since we last had one of these suggestions!
I did battle with a module that shall remain nameless the other day. I
had a difficult time figuring out how to use it. In times like these, I
like being about to go to the build directory and p(aw|ore) through the
eg/
(NOTE: I invite PIR users to read this msg, and especially item #5, and let
me know whether you'll suffer any breakage when/if Parrot default namespaces
go untyped, i.e. when you're no longer allowed to have a namespace and a
global variable with the same name but distinct. HLL-specific
David Landgren wrote:
Hey! It's been over two months since we last had one of these suggestions!
I did battle with a module that shall remain nameless the other day. I
had a difficult time figuring out how to use it. In times like these, I
like being about to go to the build directory and
Adam Kennedy wrote:
For all those component distributions I consider it a failure if it is
so complex that you need something more than just three or four lines
from the SYNOPSIS.
Maybe there should be a Kwalitee metric for the length of the synopsis?
:-)
Regards,
David Golden
Er, it's really early (excuse generator #17). So please ignore this:
On Tue, Mar 14, 2006 at 08:03:02AM -0800, Chip Salzenberg wrote:
1. Independent of other issues, you've prompted me to notice that I omitted
namespaces themselves from the namespace typed interface. Hence the
typed
Steve Peters wrote:
On Tue, Mar 14, 2006 at 04:52:18PM +0100, David Landgren wrote:
[...]
/eg scripts are a nice hands-on way of finding out how a module works
in real life.
No distribution should be without one!
Unless, of course, it has an examples/ directory, which would cause the
On Tue, Mar 14, 2006 at 12:48:52PM -0500, David Golden wrote:
Adam Kennedy wrote:
For all those component distributions I consider it a failure if it is
so complex that you need something more than just three or four lines
from the SYNOPSIS.
Maybe there should be a Kwalitee metric for the
Tels wrote:
Moin,
My modules are usually so feature crammed that they need a few examples
for showing what you can all do with it or to enable the user oto use the
modul without having to write/use perl code first.
Plus, the code cut and pasted from Synopses winds up with 8 space
leading
Perl6 could introduce (lexical, nestable) comment scope.
Has that been discussed before?
Maybe like:
##EOC
# a comment line
# another comment line
code
#EOC
Or like:
#{#
# first comment line
# next comment line
code
# last comment line
#}#
Or POD-ish.
On Fri, Mar 10, 2006 at 01:06:10PM +0100, Leopold Toetsch wrote:
('::' is the namespace delimiter according to pdd21 and not to be taken
literally)
Indeed so; but the Perl and C++ usage is so ingrained that people are still
instinctively trying to use it. So, it's time for a bigger hammer.
On Tuesday 14 March 2006 10:02, David Landgren wrote:
Plus, the code cut and pasted from Synopses winds up with 8 space
leading indents or whatever, that you have to strip out and/or you
forget to turn off vi's auto indenting so you have this massive
staircase effect and the last line starts
* David Landgren [EMAIL PROTECTED] [2006-03-14 16:55]:
No distribution should be without one!
Proc::Fork would definitely not benefit from an eg/ directory.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
On Tue, 14 Mar 2006 16:52:18 +0100, David Landgren [EMAIL PROTECTED] wrote:
Hey! It's been over two months since we last had one of these suggestions!
I did battle with a module that shall remain nameless the other day. I
had a difficult time figuring out how to use it. In times like these,
* David Landgren [EMAIL PROTECTED] [2006-03-14 19:05]:
Plus, the code cut and pasted from Synopses winds up with 8
space leading indents or whatever, that you have to strip out
and/or you forget to turn off vi's auto indenting so you have
this massive staircase effect and the last line starts at
On Tuesday 14 March 2006 08:03, Chip Salzenberg wrote:
PIR users: If namespace foo and global variable foo were no longer
distinct, so you had to rename one or the other in your code, would
you suffer any breakage in the first place, and if you did, would you
have a hard time
On Tue, Mar 14, 2006 at 08:03:02AM -0800, Chip Salzenberg wrote:
(NOTE: I invite PIR users to read this msg, and especially item #5, and let
me know whether you'll suffer any breakage when/if Parrot default namespaces
go untyped, i.e. when you're no longer allowed to have a namespace and a
Steve Peters [EMAIL PROTECTED] wrote:
/eg scripts are a nice hands-on way of finding out how a module works
in real life.
No distribution should be without one!
Unless, of course, it has an examples/ directory, which would cause the
kwalitee test to fail. ;) I do think its a good
Moin,
On Tuesday 14 March 2006 18:47, Tyler MacDonald wrote:
Steve Peters [EMAIL PROTECTED] wrote:
/eg scripts are a nice hands-on way of finding out how a module
works in real life.
No distribution should be without one!
Unless, of course, it has an examples/ directory, which
Tels [EMAIL PROTECTED] wrote:
And packages without any actual packages, like wikimedia-graph.
But I am not sure if the agreed-on last suggestions were even implemented,
or anything else done: http://cpants.dev.zsi.at/ was last updated
2005-12-05, e.g. over three months ago :(
So back at the beginning of February, there was some email traffic about
how ActiveState's automated PPM build system was using an outdated
version of Scalar-List-Utils, which was causing a cascading prerequisite
failure for many distributions.
Has anyone heard any updates on this? Does
On Tue, Mar 14, 2006 at 04:12:43PM -0500, David Golden wrote:
So back at the beginning of February, there was some email traffic about
how ActiveState's automated PPM build system was using an outdated
version of Scalar-List-Utils, which was causing a cascading prerequisite
failure for many
--- Tyler MacDonald wrote:
Well so far the only ones I've seen are eg, examples, and from that
renegade GD::Graph, samples.
And from that eccentric Acme::Bleach, demo.
/-\
On yahoo!7
Avatars: Dress up like your
David Golden [EMAIL PROTECTED] wrote:
So back at the beginning of February, there was some email traffic about
how ActiveState's automated PPM build system was using an outdated
version of Scalar-List-Utils, which was causing a cascading prerequisite
failure for many distributions.
Has
On 3/14/06, Ruud H.G. van Tol wrote:
Perl6 could introduce (lexical, nestable) comment scope.
Has that been discussed before?
I think someone might have mentioned it once. Officially you can use
# or make arbitrary POD sections.
But I'd like to make a new push for extra comment
Steve Peters wrote:
The problem was that newer Scalar-List-Utils uses an internal Perl
function that Windows does not see as an exported function. This was
changed with Perl 5.8.8. Once ActiveState releases a Perl 5.8.8, they
should be able to upgrade the version of Scalar-List-Utils that they
David Golden wrote:
Steve Peters wrote:
The problem was that newer Scalar-List-Utils uses an internal Perl
function that Windows does not see as an exported function. This was
changed with Perl 5.8.8. Once ActiveState releases a Perl 5.8.8, they
should be able to upgrade the version of
On Mon, Mar 06, 2006 at 03:31:17PM -0800, Allison Randal wrote:
On Mar 6, 2006, at 4:08, Leopold Toetsch wrote:
* Csockaddr returns a string representing a socket address
[Nicholas] I don't think that this is appropriate. It's IPv4
specific.
A more general SocketAddr PMC seems to
On Tue, Mar 14, 2006 at 12:14:24PM -0800, chromatic wrote:
On Tuesday 14 March 2006 08:03, Chip Salzenberg wrote:
PIR users: If namespace foo and global variable foo were no longer
distinct, so you had to rename one or the other in your code, would
you suffer any breakage in the
On Sun, Mar 05, 2006 at 07:11:59PM +, Nicholas Clark wrote:
=item *
Cstat retrieves information about a file on the filesystem. It takes a
string filename or an integer argument of a UNIX file descriptor, and an
integer flag for the type of information requested. It returns an
David Green wrote:
Ruud H.G. van Tol:
Perl6 could introduce (lexical, nestable) comment scope.
Has that been discussed before?
I think someone might have mentioned it once. Officially you can use
# or make arbitrary POD sections.
I don't think that covers what I mean. It was thinking about
Philippe M. Chiasson wrote:
It's not that simple a problem, exactly. The PPM build servers are all running
one the first ActivePerl release for that platform. That way, forward binary
compatibility can be guaranteed going forward.
I wondered if that was the cause of it. Still, that means
On Tuesday 14 March 2006 14:14, Chip Salzenberg wrote:
What, you currently use :: in your namespace names? On purpose? :-)
grandpaI've had objects working in my PIR code before even Dan thought they
worked. Once upon a time, that *was* the way to go.
Now get off my lawn!/grandpa
-- c
Heya. Today I noted with delight that PGE supports interpolation of
closures:
$ parrot demo.pir
rule Foo {{ print Hello }}
Though the Perl 6 form is {...} instead of {{...}} -- is that intentional?
We have started self-hosting Perl6 compilation, beginning with a
self-hosting Rule
On Tue, Mar 14, 2006 at 02:48:03PM -0800, chromatic wrote:
On Tuesday 14 March 2006 14:14, Chip Salzenberg wrote:
What, you currently use :: in your namespace names? On purpose? :-)
grandpaI've had objects working in my PIR code before even Dan thought they
worked. Once upon a time,
On Tue, Mar 14, 2006 at 06:36:22PM +0100, Ruud H.G. van Tol wrote:
: Or POD-ish.
Or POD-ish is what A2 proposes. I still like
=begin FOO
...
=end FOO
Larry
Larry wrote:
On Tue, Mar 14, 2006 at 06:36:22PM +0100, Ruud H.G. van Tol wrote:
: Or POD-ish.
Or POD-ish is what A2 proposes. I still like
=begin FOO
...
=end FOO
And I'm in the midst of writing S26 (Documentation),
wherein I propose a standard:
=begin comment
...
Isn't this what POD is for?
--
Mark Biggar
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-- Original message --
From: Ruud H.G. van Tol [EMAIL PROTECTED]
Perl6 could introduce (lexical, nestable) comment scope.
Has that been discussed before?
* Damian Conway ([EMAIL PROTECTED]) [060314 23:03]:
Larry wrote:
On Tue, Mar 14, 2006 at 06:36:22PM +0100, Ruud H.G. van Tol wrote:
: Or POD-ish.
Or POD-ish is what A2 proposes. I still like
=begin FOO
...
=end FOO
And I'm in the midst of writing S26 (Documentation),
On Tue, 14 Mar 2006, David Golden wrote:
Steve Peters wrote:
The problem was that newer Scalar-List-Utils uses an internal Perl
function that Windows does not see as an exported function. This was
changed with Perl 5.8.8. Once ActiveState releases a Perl 5.8.8,
they should be able to
David Golden wrote:
So back at the beginning of February, there was some email traffic about
how ActiveState's automated PPM build system was using an outdated
version of Scalar-List-Utils, which was causing a cascading prerequisite
failure for many distributions.
Has anyone heard any
On Mar 14, 2006, at 18:33, Chip Salzenberg wrote:
On Fri, Mar 10, 2006 at 01:06:10PM +0100, Leopold Toetsch wrote:
('::' is the namespace delimiter according to pdd21 and not to be
taken
literally)
Indeed so; but the Perl and C++ usage is so ingrained that people are
still
instinctively
Ruud H.G. van Tol wrote:
Perl6 could introduce (lexical, nestable) comment scope.
In P5 I often us q{...} in void context -- P6 seems to be attaching tags
to the quote operator, so q:comment{...} might fall out naturally.
Mark Overmeer wrote:
Looking very much forward to it... as you know.
But don't you think that the term comment is too general? The comment
text has a purpose, for instance
- comment to explain code
- comment for future implementation ideas
- references to design documents
- etc etc
On Wed, Mar 15, 2006 at 06:50:53AM +0800, Audrey Tang wrote:
Heya. Today I noted with delight that PGE supports interpolation of
closures:
$ parrot demo.pir
rule Foo {{ print Hello }}
Though the Perl 6 form is {...} instead of {{...}} -- is that intentional?
Yes, it's
52 matches
Mail list logo
