# New Ticket Created by Matt Diephouse
# Please include the string: [perl #39674]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39674 >
There''s no way to say that you want the root HLL namespace -- and
there needs to b
# New Ticket Created by Vishal Soni
# Please include the string: [perl #39671]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=39671 >
This transaction appears to have no contentThis patch fixes the branch reorganization fa
Author: chromatic
Date: Fri Jun 30 21:13:22 2006
New Revision: 13083
Modified:
trunk/docs/pdds/pdd23_exceptions.pod
Changes in other areas also in this revision:
Modified:
trunk/ (props changed)
Log:
[EMAIL PROTECTED]: chromatic | 2006-06-30 21:13:10 -0700
Fixed POD formatting errors
On 7/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
+In particular, these forms disable the lookahead for an adverbial argument,
+so while
+
+q:n($foo)
+
+will misinterpret C<$foo> as the C<:n> argument,
+
+qn(stuff)
+
+has the advantage of misinterpreting it as the argument to the C
From: Chip Salzenberg <[EMAIL PROTECTED]>
Date: Fri, 30 Jun 2006 22:11:39 -0500
. . .
Allison, if you give me the OK, I'll recast pdd23 in the alternative way I
had in mind, where:
* exception handlers are closures,
* the closures are called _inside_ the dynamic scope whe
On Sat, Jul 01, 2006 at 12:22:56AM -0700, [EMAIL PROTECTED] wrote:
> Another FAILING namespace test:
> $P0 = new .ResizableStringArray
> $P0[0] = ''
> $P1 = get_namespace $P0
I think I (or the pdd) may have been misunderstood:
The get_namespace opcode currently accepts keys (and strings).
Since Parrot's mission is far bigger (and, in some ways, far smaller :-))
than Perl 6, and I like the idea that the project advertise itself
truthfully, so as not to turn away those who aren't interested in Perl: at
my request Robert has set up the alias
[EMAIL PROTECTED] -> perl6-internals
Here at the tail end of the Hackathon, Patrick suggests that while p6i is no
longer descriptive, it does have the advantage of abbreviating to a nify
token (i.e. "p6i"). So what, he asks, should be the abbreviation for
parrot-porters?
Seems to me that common usage will settle out for itself -- th
At Chip's YAPC talk, I mentioned that Java would soon be adding support
directly to the language for "scripting" languages in their Java 6 or
1.6 release. Finding actual Sun documentation on the framework has been
a little tough, but here's a sampling of a few articles that have been
written j
Chip Salzenberg <[EMAIL PROTECTED]> wrote:
On Sat, Jul 01, 2006 at 12:22:56AM -0700, [EMAIL PROTECTED] wrote:
> Another FAILING namespace test:
> $P0 = new .ResizableStringArray
> $P0[0] = ''
> $P1 = get_namespace $P0
I think I (or the pdd) may have been misunderstood:
The get_namespace
Chip Salzenberg wrote:
Allison, if you give me the OK, I'll recast pdd23 in the alternative way I
had in mind, where:
* exception handlers are closures,
* the closures are called _inside_ the dynamic scope where the throw occurred,
* a closure returning without executing C implies "I didn'
Author: chip
Date: Sat Jul 1 11:26:02 2006
New Revision: 13092
Modified:
trunk/docs/pdds/pdd23_exceptions.pod
Log:
* Exception handlers are now closures (or just plain subroutines),
not continuations.
* Eliminate the C opcode, as the handler returning is enough
of a clue that the next han
Author: chip
Date: Sat Jul 1 11:26:44 2006
New Revision: 13093
Modified:
trunk/docs/pdds/pdd23_exceptions.pod
Log:
oops, restore namespace on exception class in example code
Modified: trunk/docs/pdds/pdd23_exceptions.pod
==
Author: chip
Date: Sat Jul 1 11:30:02 2006
New Revision: 13094
Modified:
trunk/docs/pdds/pdd23_exceptions.pod
Log:
rename 'caught' opcode to 'handled' for obscure reasons
Modified: trunk/docs/pdds/pdd23_exceptions.pod
=
YAPC is, among other things, a wonderful opportunity to meet and talk
face-to-face about things that concern us. This YAPC, one topic was how to
get Parrot development on track to make it the VM we all believe it can be.
One outcome of these discussions is a bit of a personnel shuffle, to wit:
I'
Author: larry
Date: Sat Jul 1 12:20:14 2006
New Revision: 9732
Modified:
doc/trunk/design/syn/S05.pod
Log:
Deconfusing "match state" and state vars from Bruce Gray++.
Modified: doc/trunk/design/syn/S05.pod
==
--- do
On Sat, Jul 01, 2006 at 10:56:26AM -0700, Matt Diephouse wrote:
> At the top of the pdd:
> - Add a get_namespace opcode (that takes an -->array<-- or a
>multidimensional hash index)
> [...]
>=item $P0 = get_namespace $P1
>
>Get the namespace $P1 (an -->array<-- of names or [...]
Gee
Author: chip
Date: Sat Jul 1 12:27:31 2006
New Revision: 13097
Modified:
trunk/docs/pdds/pdd21_namespaces.pod
Log:
Consistently describe namespace identifiers accepted by namespace opcodes as
either key constants or string arrays, since both of those work in all cases
(or should :-)).
Modif
Author: larry
Date: Sat Jul 1 12:13:49 2006
New Revision: 9731
Modified:
doc/trunk/design/syn/S03.pod
Log:
Revisions from Bruce Gray++.
Modified: doc/trunk/design/syn/S03.pod
==
--- doc/trunk/design/syn/S03.pod
Those of you who were/are at the YAPC Hackathon might know, I've begun
work on what started as Test::Harness 3 and is now TAP::Harness. This
is brand new, ground up rewrite of the idea of a harness for TAP
sources (a foo.t file is a TAP source). Its being designed to be
extendable to handle all
This might seem like an odd question but will it be tightly tied to
TAP or will it be possible to use another protocol or an extension to
TAP?
F
On 01/07/06, Michael G Schwern <[EMAIL PROTECTED]> wrote:
Those of you who were/are at the YAPC Hackathon might know, I've begun
work on what started
On Sat, Jul 01, 2006 at 08:45:02PM +0100, Fergal Daly wrote:
> This might seem like an odd question but will it be tightly tied to
> TAP or will it be possible to use another protocol or an extension to
> TAP?
Pluggable testing protocols, perhaps. They would need to follow some
similar ground ru
Author: chip
Date: Sat Jul 1 13:00:41 2006
New Revision: 13098
Modified:
trunk/docs/pdds/pdd21_namespaces.pod
Log:
Specify new compiler methods, compiler.'parse_name'(), which allows parsing
foreign language names using the foreign language's rules. (per Allison)
[Tests Welcome]
Modified
On Jul 1, 2006, at 2:45 PM, Fergal Daly wrote:
This might seem like an odd question but will it be tightly tied to
TAP or will it be possible to use another protocol or an extension to
TAP?
Yes. It is about TAP. That's why it's TAP::Harness.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.
On Sat, Jul 01, 2006 at 02:36:37PM -0500, Michael G Schwern wrote:
> Right now the use cases I have in mind include things such as
> parallelized test runs, fancy GUI and HTML outputs (for example,
> Provide use cases, what would you want to do with Test::Harness if you
> could? What are you doi
On 01/07/06, Andy Lester <[EMAIL PROTECTED]> wrote:
On Jul 1, 2006, at 2:45 PM, Fergal Daly wrote:
> This might seem like an odd question but will it be tightly tied to
> TAP or will it be possible to use another protocol or an extension to
> TAP?
Yes. It is about TAP. That's why it's TAP::H
On Sat, Jul 01, 2006 at 03:31:52PM +0300, Markus Laire wrote:
: On 7/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
: >+In particular, these forms disable the lookahead for an adverbial
: >argument,
: >+so while
: >+
: >+q:n($foo)
: >+
: >+will misinterpret C<$foo> as the C<:n> argument,
:
Chip Salzenberg <[EMAIL PROTECTED]> wrote:
The actual bug you've found seems unrelated to the use of the array of
strings (vs. a key), as substituting the key version:
$P0 = get_namespace ['']
still fails. Debugging in progress.
It looks like IMCC treats C< .namespace [''] > as the root H
On Sat, Jul 01, 2006 at 01:30:40PM -0700, Matt Diephouse wrote:
> Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> >The actual bug you've found seems unrelated to the use of the array of
> >strings (vs. a key), as substituting the key version:
> > $P0 = get_namespace ['']
> >still fails. Debugging i
Author: larry
Date: Sat Jul 1 13:55:09 2006
New Revision: 9733
Modified:
doc/trunk/design/syn/S02.pod
doc/trunk/design/syn/S06.pod
Log:
Clarification of differences between quote and macro declarations, Markus++.
Modified: doc/trunk/design/syn/S02.pod
On Saturday 01 July 2006 22:36, Michael G Schwern wrote:
> Those of you who were/are at the YAPC Hackathon might know, I've begun
> work on what started as Test::Harness 3 and is now TAP::Harness. This
> is brand new, ground up rewrite of the idea of a harness for TAP
> sources (a foo.t file is a
On Saturday 01 July 2006 14:24, Shlomi Fish wrote:
> I'd hate to see some duplicate effort.
Test::Run has really curious licensing; I'm not interested in redistributing
that code under all of those licenses.
-- c
Please look at Test::TAP::Model and the horrrible hooks it goes
through to make things work.
I'd love to have a SAX like event-handler model for TAP through
TAP::Harness so that I can construct Test::TAP::Model objects in a
cleaner way (without the parser-is-the-model and all that mess).
--
Chip Salzenberg <[EMAIL PROTECTED]> wrote:
I've rooted out that bug, but then discovered there's no way left to
designate the root HLL namespace, so I've invented
.namespace # no key
to mean the HLL root.
That resolves the other ticket I opened yesterday (good). But I'd
prefer to have C< .
I picked this up at the YAPC and made some markups on it. Apologies
that it is not in a diff format, but that's going to come with practice.
I got stuck on some of the intended behaviors and prohibited behaviors
of the 'goto' function. For the purpose of clarity would it be useful
to provide
On 7/1/06, Yuval Kogman <[EMAIL PROTECTED]> wrote:
Please look at Test::TAP::Model and the horrrible hooks it goes
through to make things work.
I'd love to have a SAX like event-handler model for TAP through
TAP::Harness so that I can construct Test::TAP::Model objects in a
cleaner way (with
On 7/1/06, Steve Peters <[EMAIL PROTECTED]> wrote:
On Sat, Jul 01, 2006 at 08:45:02PM +0100, Fergal Daly wrote:
> This might seem like an odd question but will it be tightly tied to
> TAP or will it be possible to use another protocol or an extension to
> TAP?
Pluggable testing protocols, perhap
Darn, find_global has collided with pdd21.
Currently find_global is prepared to accept a key or a namespace, and
distinguishing namespaces from arrays is starting to get just a little
too polymorphic for an opcode.
I'm thinking that between get_namespace and the untyped namespace interface,
find_
On Saturday 01 July 2006 14:52, Michael G Schwern wrote:
> There are at least two approaches I could think of that fit the
> existing design. One is to replace the tokenizer. The other is to
> create a TAP source which converts from your protocol into TAP. The
> latter is probably easiest and s
On 7/1/06, Shlomi Fish <[EMAIL PROTECTED]> wrote:
One thing I'm wondering about is
whether you are going to code all of this into TAP::Harness from scratch.
I believe I mentioned, I intend to steal lots of code from
Test::Harness and Straps. "Steal" in the cut & paste sense. I have
already ad
The PITA / TestBuilder2 BOF at YAPC whacked up this TAP extension.
Test groups in TAP. There are several use-cases here.
1. I want to name a group of tests rather than the individuals.
2. I don't want to have to count up the total number of tests in my
file but I do want the protection of the
On 7/1/06, Yuval Kogman <[EMAIL PROTECTED]> wrote:
Another issue we had at work when I was abusing TAP for our C++ UT
framework was that we needed more levels of nesting (TAP only
supports streams and test cases - I was handling many test cases in
the same stream, for nested modules... I faked "f
On Sat, Jul 01, 2006 at 16:59:24 -0500, Michael G Schwern wrote:
> Yes, it is SAXy. You have Adam to thank for that.
>
> As my flight is delayed I'll try to make a stab at posting up the basic
> design.
Another issue we had at work when I was abusing TAP for our C++ UT
framework was that we ne
Author: nicholas
Date: Sat Jul 1 12:24:40 2006
New Revision: 13096
Modified:
trunk/docs/pdds/pdd23_exceptions.pod
Log:
Fix two typos.
Modified: trunk/docs/pdds/pdd23_exceptions.pod
==
--- trunk/docs/pdds/pdd23_excep
Leopold Toetsch wrote:
> On Jun 29, 2006, at 18:48, Jarkko Hietaniemi wrote:
>
>> Any way to add verbosity to e.g. see which commands are being run?
>
> perl Configure.pl --verbose-step=snprintf
...
Testing snprintf...cc -std -D_INTRINSICS -fprm d -ieee -I/p/include
-DLANGUAGE_C -pthread -D_XOPE
It looks like it's only one level of nesting. Any reason not to go the
whole hog with something like
..1
OK 1
..2
...1
OK 2
OK 3
...2
OK 4
..3
OK5
F
On 01/07/06, Michael G Schwern <[EMAIL PROTECTED]> wrote:
The PITA / TestBuilder2 BOF at YAPC whacked up this TAP extension.
Test groups in TAP.
Chip Salzenberg wrote:
Darn, find_global has collided with pdd21.
Currently find_global is prepared to accept a key or a namespace, and
distinguishing namespaces from arrays is starting to get just a little
too polymorphic for an opcode.
I'm thinking that between get_namespace and the untyped n
On Jul 1, 2006, at 1:40 PM, Chip Salzenberg wrote:
One outcome of these discussions is a bit of a personnel shuffle
I've taken the liberty of assigning all the PDD tickets in RT to
Allison, and the two upcoming release tickets to Chip.
I've also updated http://dev.perl.org/perl6/people.
On Saturday 01 July 2006 16:46, Fergal Daly wrote:
> It looks like it's only one level of nesting. Any reason not to go the
> whole hog with something like
>
> ..1
> OK 1
> ..2
> ...1
> OK 2
> OK 3
> ...2
> OK 4
> ..3
> OK5
No one has provided an actual use case for it yet. YAGNI.
-- c
On Sat, Jul 01, 2006 at 21:37:48 -0700, chromatic wrote:
> No one has provided an actual use case for it yet. YAGNI.
*cough* I did.
See the TAP::Harness thread... We had UT fixtures with subsections
at work, which were further grouped by class, but all emitted in the
same stream.
That was very
50 matches
Mail list logo
