On Mon, Feb 14, 2005 at 09:17:54PM -0800, Ovid wrote:
> --- chromatic <[EMAIL PROTECTED]> wrote:
> > Can you tell I'm wearing my editor's hat?
>
> Awfully big hat :)
Goes with the pants.
--- chromatic <[EMAIL PROTECTED]> wrote:
> Can you tell I'm wearing my editor's hat?
Awfully big hat :)
=
If this message is a response to a question on a mailing list, please send
follow up questions to the list.
Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
On Mon, 2005-02-14 at 23:04 -0600, Andy Lester wrote:
> Darn you and your clear thinking.
Truly clear thinking would have realized that Description, Directive,
Diagnostics is a very nice mnemonic. (It's doubly nice because
"diagnostics" appears in the plural form so much more often than the
sing
On Feb 14, 2005, at 9:01 PM, chromatic wrote:
Here's my list of suggestions for each:
1) label, description
2) directive, instruction
3) diagnostic
I want to avoid the word "comment" altogether, making the optionalness
of #1 and #3 evident in their words, the activeness of #2 evident in
its
word,
I want to avoid the word "comment" altogether, making the optionalness
of #1 and #3 evident in their words, the activeness of #2 evident in
its
word, and any comparison to Perl's comments in syntax or name go away.
Darn you and your clear thinking.
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.pe
On Mon, 2005-02-14 at 14:38 -0600, Andy Lester wrote:
> Anything that starts with # is ignored by the harness. That's very
> different from the test comment.
Yet Test::Harness::TAP calls them comments and comment lines!
Put on my boots for a second. Here's what I'm trying to explain:
On Mon, Feb 14, 2005 at 03:32:35PM -0500, Michael G Schwern ([EMAIL PROTECTED])
wrote:
> > But it makes explaining the TAP format a pain. The "test comment" is
> > everything after the test number or "ok" and before the # comment
> > marker or end of the line.
Anything that starts with # is ign
On Mon, Feb 14, 2005 at 10:04:44AM -0800, Ovid wrote:
> Is this not correct? Where is the TAP protocol documented?
http://search.cpan.org/~petdance/Test-Harness-2.46/lib/Test/Harness/TAP.pod
(Any Test-Harness distribution 2.46 or later, IIRC)
Nicholas Clark
On Mon, Feb 14, 2005 at 09:48:39AM -0800, Ovid wrote:
> It makes good enough sense when you're dealing with the call to the
> test:
>
>ok($blah, "This is a test comment");
>
> But it makes explaining the TAP format a pain. The "test comment" is
> everything after the test number or "ok" and
Quoting chromatic <[EMAIL PROTECTED]>:
> On Mon, 2005-02-14 at 11:49 -0600, Andy Lester wrote:
>
> > It's a comment.
>
> *What* is a comment? Is it the semantically insignificant text that can
> contain skip or TODO or the semantically significant text with a
> preceding # somewhere?
> They're se
--- Andy Lester <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 14, 2005 at 09:48:39AM -0800, Ovid
> ([EMAIL PROTECTED]) wrote:
> > It's actually rather important that I have an answer for this, but
> I
> > really can't go into more detail (sorry).
>
> It's a comment.
There's more than one thing being d
On Mon, 2005-02-14 at 11:49 -0600, Andy Lester wrote:
> It's a comment.
*What* is a comment? Is it the semantically insignificant text that can
contain skip or TODO or the semantically significant text with a
preceding # somewhere?
Is it both? I find that full of explanatory confusion potentia
On Mon, Feb 14, 2005 at 09:48:39AM -0800, Ovid ([EMAIL PROTECTED]) wrote:
> It's actually rather important that I have an answer for this, but I
> really can't go into more detail (sorry).
It's a comment.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
What follows are the notes I have from someone else regarding the name
"comment" for what was previously considered the "label."
It's actually rather important that I have an answer for this, but I
really can't go into more detail (sorry).
Cheers,
Ovid
> It's been settled. It's officially a "te
David H. Adler wrote:
A question: is there any reason that you made this an OO module but
still show calls to the methods as functions rather than methods on the
object?
I.e. why C rather than
C<$capture->verify_number_lines> ? This would also remove the need to
explicitly export those functions.
J
15 matches
Mail list logo
