Geoffrey Young wrote:
[ Just before sending this I notice Geoff has recommended something
better, but I'll send this too as another WTDI. ]
cool :)
I started to maintain Apache-Test skeletons, but I never quite got them up
to speed. give me a few days and I'll roll a tarball with a
On Tue, Oct 05, 2004 at 11:27:01AM -0400, Geoffrey Young wrote:
as promised, here is a tarball that includes a 'test-cover' target.
http://perl.apache.org/~geoff/Apache-Test-with-Devel-Cover.tar.gz
it's made a little more complex than it needs to be because of version
restrictions:
David Wheeler wrote:
On Oct 2, 2004, at 2:30 PM, Geoffrey Young wrote:
I started to maintain Apache-Test skeletons, but I never quite got
them up
to speed. give me a few days and I'll roll a tarball with a test-cover
target so that folks can have an entire working example of the way I
On Oct 5, 2004, at 11:08 AM, Geoffrey Young wrote:
I think that all Apache::TestMB would need to do is add a make target
that
looks like this:
test-cover ::
@cover -delete
@HARNESS_PERL_SWITCHES=-MDevel::Cover=+inc,$(HOME)/.apache-test
APACHE_TEST_EXTRA_ARGS=-one-process $(MAKE)
On Tue, Oct 05, 2004 at 02:08:25PM -0400, Geoffrey Young wrote:
David Wheeler wrote:
Perhaps I should add support for Module::Build's covertest action to
Apache::TestMB...just tell me what it needs to do.
I think that all Apache::TestMB would need to do is add a make target that
looks
On Oct 5, 2004, at 11:25 AM, Paul Johnson wrote:
I wonder whether we shouldn't try to standardise the target name before
it's too late to do so. Module::Build uses covertest, I've always used
cover, and Geoff has just used test-cover.
Actually, Module::Build uses testcover.
I'm not overly
- HARNESS_PERL_SWITCHES gets Devel::Cover started
Module::Build's testcover target already does this.
:)
- +inc,$(HOME)/.apache-test keeps coverage away from generated A-T
files,
which isn't required
Ah, cool. But $(HOME) doesn't correspond to ~/ here, does it?
yeah - it's
test-cover ::
@cover -delete
@HARNESS_PERL_SWITCHES=-MDevel::Cover=+inc,$(HOME)/.apache-test
APACHE_TEST_EXTRA_ARGS=-one-process $(MAKE) test
@cover
I wonder whether we shouldn't try to standardise the target name before
it's too late to do so. Module::Build uses
On Oct 5, 2004, at 11:32 AM, Geoffrey Young wrote:
Ah, cool. But $(HOME) doesn't correspond to ~/ here, does it?
yeah - it's equivalent to $ENV{HOME} in make-land. I guess there is
always
the danger that $HOME isn't populated, but internally A-T uses
$ENV{HOME}
when it generates the
On Tue, Oct 05, 2004 at 11:32:23AM -0700, David Wheeler wrote:
On Oct 5, 2004, at 11:25 AM, Paul Johnson wrote:
I wonder whether we shouldn't try to standardise the target name before
it's too late to do so. Module::Build uses covertest, I've always used
cover, and Geoff has just used
David Wheeler wrote:
On Oct 5, 2004, at 11:32 AM, Geoffrey Young wrote:
Ah, cool. But $(HOME) doesn't correspond to ~/ here, does it?
yeah - it's equivalent to $ENV{HOME} in make-land. I guess there is
always
the danger that $HOME isn't populated, but internally A-T uses $ENV{HOME}
On Oct 5, 2004, at 11:51 AM, Geoffrey Young wrote:
basically it goes into $HOME because it stores the A-T preferences for
a
specific user. but this is all part of the endless 'sticky
preferences' foo
that I really don't want to be associated with ;) lots of to and fro
in the
httpd-test
On Oct 5, 2004, at 11:51 AM, Geoffrey Young wrote:
basically it goes into $HOME because it stores the A-T preferences for
a
specific user. but this is all part of the endless 'sticky
preferences' foo
that I really don't want to be associated with ;) lots of to and fro
in the
httpd-test
+my $atdir = $self-localize_file_path($ENV{HOME}/.apache-test);
+local $Test::Harness::switches=
+local $Test::Harness::Switches=
+local $ENV{HARNESS_PERL_SWITCHES} = -MDevel::Cover=+inc,'$atdir';
somewhere in here it looks like -one-process is missing, though I
On Oct 5, 2004, at 12:36 PM, Geoffrey Young wrote:
somewhere in here it looks like -one-process is missing, though I
wouldn't
know where it would go.
I'll put it in, though it isn't needed if you use A-T in CVS, eh?
you're the only one with commit access who uses or understand
Module::Build,
so
David Wheeler wrote:
On Oct 5, 2004, at 12:36 PM, Geoffrey Young wrote:
somewhere in here it looks like -one-process is missing, though I
wouldn't
know where it would go.
I'll put it in, though it isn't needed if you use A-T in CVS, eh?
no, it is required. but only cvs currently
On Oct 5, 2004, at 12:43 PM, Geoffrey Young wrote:
no, it is required. but only cvs currently supports -one-process as an
option - earlier versions will explode.
Okay. So I just added this to the testcover action:
local $ENV{APACHE_TEST_EXTRA_ARGS} = -one-process;
Is that all it needs?
David Wheeler wrote:
On Oct 5, 2004, at 12:43 PM, Geoffrey Young wrote:
no, it is required. but only cvs currently supports -one-process as an
option - earlier versions will explode.
Okay. So I just added this to the testcover action:
local $ENV{APACHE_TEST_EXTRA_ARGS} =
On Oct 5, 2004, at 12:53 PM, Geoffrey Young wrote:
yeah, I think that's all the required up front pieces. authors still
need
to configure Devel::Cover over in httpd.conf land, but there's not
much we
can do from a makefile to help with that.
I think we're good to go, then.
Regards,
David
Felix Gallo [EMAIL PROTECTED] wrote:
6. It's a little alarming that if you look for struct
ParrotIOData in src/ and include/, you won't find it. I found
it, but couldn't figure out why it was there. Leo?
Bigger parts of the interpreter like imcc and IO are distinct subsystems
and are
Dan Sugalski [EMAIL PROTECTED] wrote:
Next I want to add in the op variants:
$Px = find_global [key; key]
$Px = find_global $Px, [key; key]
$Px = find_global $Py, 'name'
I've already proposed some time ago that these variants of namespace
manipulation aren't really necessary. I
Jens Rieks [EMAIL PROTECTED] wrote:
- added all people mentioned by courtesy of lines in parrot-cvs messages back to
Feb 5th, 2004
Great, thanks.
-N: Stéphane
+N: St�hane
Encodings strike back ;)
leo
Michel Pelletier [EMAIL PROTECTED] wrote:
Parakeet is an object-oriented Forth-like stack language for the Parrot
VM. It is written in PIR and compiled its code directly to PIR.
Committed to CVS now.
I've replaced the end opcode with this sequence:
clear_eh
exit 0
and added a comment,
We still have the problem to access runtime files with an installed
parrot. So what about this idea:
* we have another source file (parrot_config.c) that gets linked to parrot
* this source file has basically just one CONST_STRING holding the
frozen image of the parrot configuration
On Tuesday 05 October 2004 13:22, Leopold Toetsch wrote:
Comments?
What about using miniparrot to create parrot_config.c?
jens
On Saturday 02 October 2004 13:10, Stephane Peiry wrote:
This patch adds tests for iscompare style ops (isgt, isge, isle, islt,
iseq, isne) on integers, numbers and strings, in t/op/comp.t.
Thanks, applied.
jens
On Mon, 04 Oct 2004 21:39:59 +0100, Piers Cawley [EMAIL PROTECTED] wrote:
Stéphane Payrard [EMAIL PROTECTED] writes:
On Fri, Oct 01, 2004 at 06:09:37PM +0200, Jerome Quelin wrote:
This function is defined in emacs:
line-beginning-position is a built-in function.
Jens Rieks [EMAIL PROTECTED] wrote:
On Tuesday 05 October 2004 13:22, Leopold Toetsch wrote:
Comments?
What about using miniparrot to create parrot_config.c?
Yep. Finally yes. But building miniparrot is another untested step in
that process. For now and the release using the regular parrot is
# New Ticket Created by Dan Sugalski
# Please include the string: [perl #31848]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=31848
We do all the rest... might as well do this one too.
--
Since Sam Ruby's been poking at it, and I'm waiting on the register
coloring function to churn, I figured I'd poke at the python
converter in CVS a bit. So I did. More ops are done, and things get a
bit further on his big list 'o tests than they did before, which is
nice. My translator handles
On Tue, 2004-10-05 at 07:40, Dan Sugalski wrote:
We do all the rest... might as well do this one too.
It'd look a little something like this.
Where do PIR tests go, by the way? I didn't see them in a trivial grep.
(For future reference through search engines, rebuilding Parrot was a
pain
Dan Sugalski [EMAIL PROTECTED] wrote:
We do all the rest... might as well do this one too.
PIR syntax is in. But we don't have 2-arg forms of these opcode.
leo
Dan Sugalski [EMAIL PROTECTED] wrote:
Since Sam Ruby's been poking at it, and I'm waiting on the register
coloring function to churn, I figured I'd poke at the python
converter in CVS a bit. So I did. More ops are done, and things get a
bit further on his big list 'o tests than they did
At 5:44 PM +0200 10/5/04, Leopold Toetsch wrote:
Dan Sugalski [EMAIL PROTECTED] wrote:
Since Sam Ruby's been poking at it, and I'm waiting on the register
coloring function to churn, I figured I'd poke at the python
converter in CVS a bit. So I did. More ops are done, and things get a
bit
Dan Sugalski wrote:
Since Sam Ruby's been poking at it, and I'm waiting on the register
coloring function to churn, I figured I'd poke at the python converter
in CVS a bit. So I did. More ops are done, and things get a bit further
on his big list 'o tests than they did before, which is nice. My
At 12:34 PM -0400 10/5/04, Sam Ruby wrote:
Dan Sugalski wrote:
Since Sam Ruby's been poking at it, and I'm waiting on the register
coloring function to churn, I figured I'd poke at the python
converter in CVS a bit. So I did. More ops are done, and things get
a bit further on his big list 'o
Leo writes:
Felix Gallo [EMAIL PROTECTED] wrote:
6. It's a little alarming that if you look for struct
ParrotIOData in src/ and include/, you won't find it. I found
it, but couldn't figure out why it was there. Leo?
Bigger parts of the interpreter like imcc and IO are distinct
Chromatic [EMAIL PROTECTED] wrote:
It'd look a little something like this.
Thanks, applied ops - rest was already in.
Where do PIR tests go, by the way? I didn't see them in a trivial grep.
I did :
$ find t -name '*.t' | xargs grep /=
$ find imcc/t -name '*.t' | xargs grep /=
(For future
On Oct 4, 2004, at 8:25 AM, Dan Sugalski wrote:
Okay, since we've got the *basic* semantics down (unified namespace,
namespace entries get a post-pended null character)
I'll ask again, what about subs? Do they get name-mangled too?
$Px = find_global [key; key; key], 'name'
As Leo pointed out
Wed 6.10. 18:00 GMT - feature freeze
Sat 9.10. 8:00 GMT - code freeze - no checkins please
- Parrot 0.1.1 will go out on Saturday.
- nice release name wanted
leo
On Oct 4, 2004, at 9:58 PM, Brent 'Dax' Royal-Gordon wrote:
Tim Bunce [EMAIL PROTECTED] wrote:
Now, with that out of the way, let's talk about overlaid namespaces.
I don't think I ever read a description of what the purpose of this
was.
I get the what but not the why. Without the why it's hard to
Leo writes:
Wed 6.10. 18:00 GMT - feature freeze
Sat 9.10. 8:00 GMT - code freeze - no checkins please
- Parrot 0.1.1 will go out on Saturday.
- nice release name wanted
'fireparrot'
Jeff Clites [EMAIL PROTECTED] wrote:
On Oct 4, 2004, at 9:58 PM, Brent 'Dax' Royal-Gordon wrote:
You can have the current namespace actually be [ ::Foo::Bar::Baz,
::Foo::Bar, ::* ] (or, for the last one, whatever the namespace that
@*ARGS and friends are in is called), so that the search
Leopold Toetsch wrote:
Wed 6.10. 18:00 GMT - feature freeze
Sat 9.10. 8:00 GMT - code freeze - no checkins please
- Parrot 0.1.1 will go out on Saturday.
- nice release name wanted
There is a nice list of parrots on the Wikipedia [
http://en.wikipedia.org/wiki/Parrot ].
I say we go with
Leopold Toetsch:
- nice release name wanted
Firebird or Phoenix
sebastian
--- Leopold Toetsch [EMAIL PROTECTED] wrote:
- nice release name wanted
Poicephalus
Overall temperament: As a whole have an endearing
quality. They have the potential to be very good, well
socialized. They are not noisy and raucous nor do they
scream for attention. They are able to speak with
Nice list.
My favorites were:
Black Lory
Purple-bellied
Green Pygmy
Modest Tiger
Malabar
Nicobar
Red-headed Lovebird
Red-faced
Scaly-headed
Festive
Mealy
Red-fan
Blue-bellied
--
Garrett Goebel
IS Development Specialist
ScriptPro Direct: 913.403.5261
On Fri, 2004-10-01 at 18:22, John Paul Wallington wrote:
Jerome Quelin [EMAIL PROTECTED] writes:
And the minibuffer tells me:
Symbol's function definition is void: line-beginning-position
I'm using xemacs 21.4.14
You could put something like:
(defalias 'line-beginning-position
# New Ticket Created by Matthew Zimmerman
# Please include the string: [perl #31853]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=31853
---
osname= linux
osvers= 2.4.21-4.elsmp
arch= i386-linux-thread-multi
chromatic wrote:
On Tue, 2004-10-05 at 07:40, Dan Sugalski wrote:
We do all the rest... might as well do this one too.
It'd look a little something like this.
Where do PIR tests go, by the way? I didn't see them in a trivial grep.
delurk
Apparently in imcc/t... The simple op tests are in
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #31850]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=31850
This patch removes two files that are no longer generated from
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #31849]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=31849
The following patch makes compilation both slightly quieter and also
slightly
ooh, a patch for Tcl! You're hired. =-)
Applied in spirit - I removed all the references to the ops directory entirely, since
I'm not using it anymore. (All the ops are now part of lib/expression.imc)
Thanks! (must remember to run cvs update -P to catch these things.)
Matthew Zimmerman (via RT)
# New Ticket Created by Will Coleda
# Please include the string: [perl #31859]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=31859
Original Message
Subject: Re: Plain ole Hash
Date: Mon, 04
# New Ticket Created by Will Coleda
# Please include the string: [perl #31860]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=31860
I tried to clear out some of dependency issues in Makefile, and got lost.
On Oct-05, Andy Dougherty wrote:
The following patch makes compilation both slightly quieter and also
slightly more informative.
Or, with less spin, it fixes bad advice I gave previously. Specifically,
I had previously noted that it's generally helpful if the Makefile prints
out the
On Oct-05, Andy Dougherty wrote:
This patch removes two files that are no longer generated from
MANIFEST.generated.
Thanks, applied.
On Oct-05, Leopold Toetsch wrote:
Wed 6.10. 18:00 GMT - feature freeze
Sat 9.10. 8:00 GMT - code freeze - no checkins please
- Parrot 0.1.1 will go out on Saturday.
- nice release name wanted
0.1.1 - Hydroparrot
0.1.2 - Helioparrot
0.1.3 - Parrolith
0.1.4 - Perylous
0.1.5 - Porn (um...
Any chance of getting:
'cd dynclasses; make'
working on OS X by then?
I've been pestering Dan about it on IRC, but figured a ping to the list wouldn't hurt.
Leopold Toetsch wrote:
Wed 6.10. 18:00 GMT - feature freeze
Sat 9.10. 8:00 GMT - code freeze - no checkins please
- Parrot 0.1.1 will go out
59 matches
Mail list logo
