* Eric Wilhelm [EMAIL PROTECTED] [2008-04-06 18:45]:
(perhaps allow non-first numbers too?) /^[a-z][a-z0-9_]*$/ ?
++
Preceding the key with an underscore or some kind of squiggle
should be enough to make it safe. Having ToWrite AllPrivateKeys
InStudlyCaps
On Monday 07 April 2008, Aristotle Pagaltzis wrote:
* Eric Wilhelm [EMAIL PROTECTED] [2008-04-06 18:45]:
(perhaps allow non-first numbers too?) /^[a-z][a-z0-9_]*$/ ?
++
Preceding the key with an underscore or some kind of squiggle
should be enough to make it safe. Having ToWrite
Hi all,
Mostly an FYI: I'm in Oslo right now and we're working out (and
implementing) new features in TAP. One of them is the new YAML
diagnostics. They look like this (these aren't all we support):
not ok 2 We ain't got foobar!
---
file: t/something.t
line: 14
tags:
Eric Wilhelm wrote:
# from Ovid
# on Sunday 06 April 2008 08:41:
file: t/something.t
If the filename is the same on every test in the stream, why is this
being attached to the test and not the stream?
It's the default (when attached to a stream), but can be overridden by each
individual
# from Nicholas Clark
# on Sunday 06 April 2008 09:33:
reserved (and it's a parse error to use an unknown lower-case key).
Are there any strange Unicode issues where we might get confused
about what is upper and lower case?)
I believe that there are code points which would be considered word
--- Eric Wilhelm [EMAIL PROTECTED] wrote:
# from Ovid
# on Sunday 06 April 2008 08:41:
file: t/something.t
If the filename is the same on every test in the stream, why is this
being attached to the test and not the stream?
Or, the filename *could* change between tests in a stream?
On Sun, Apr 06, 2008 at 08:41:11AM -0700, Ovid wrote:
Currently you can shove anything in there you want, but you must use
upper-case keys for your personal use and all lower-case keys are
reserved (and it's a parse error to use an unknown lower-case key).
Are there any strange Unicode
# from Ovid
# on Sunday 06 April 2008 08:41:
file: t/something.t
If the filename is the same on every test in the stream, why is this
being attached to the test and not the stream?
Or, the filename *could* change between tests in a stream? Does it?
Should it?
--Eric
--
A counterintuitive
On 9/3/07, Ovid [EMAIL PROTECTED] wrote:
--- A. Pagaltzis [EMAIL PROTECTED] wrote:
Is it possible to force this in tandem? Ie. when one of the keys
has to be quoted, the other is always quoted also? Because I'd
hate to see this:
wanted: elbow
found: 'elbow '
For
--- demerphq [EMAIL PROTECTED] wrote:
If string data was *always* quoted and numeric data never was
(assuming
it's really numeric), then most of the issues raised in this thread
would go away.
Define string data and numeric data. :-)
IOW, is 0E0 string or numeric?
This can be tricky
On 9/4/07, Ovid [EMAIL PROTECTED] wrote:
--- demerphq [EMAIL PROTECTED] wrote:
If string data was *always* quoted and numeric data never was
(assuming
it's really numeric), then most of the issues raised in this thread
would go away.
Define string data and numeric data. :-)
--- demerphq [EMAIL PROTECTED] wrote:
I think the solution is to leave it up to a given language as to
whether they discriminate or not, document how they can, and leave it
alone. Its not going to be easy to do in some languages, so they
probably dont have to or want to care, and in the
On 4 Sep 2007, at 09:24, demerphq wrote:
I really think this is an area where the more you think about it the
more problems you discover and the less you think about it the less
likely you will encounter any problems at all.
I think that's about right. I don't think it's a showstopper for us.
A. Pagaltzis wrote:
Is it possible to force this in tandem? Ie. when one of the keys
has to be quoted, the other is always quoted also? Because I’d
hate to see this:
wanted: elbow
found: 'elbow '
For simple cases like this one it’s livable, but if the data gets
more complex,
Hi Michael,
* Michael G Schwern [EMAIL PROTECTED] [2007-09-01 19:32]:
On 9/1/07, Fergal Daly [EMAIL PROTECTED] wrote:
On a tangent, I think using quotes is important otherwise you
end up output like
wanted: elbow
found: elbow
when what you really needed was
wanted:
--- A. Pagaltzis [EMAIL PROTECTED] wrote:
Is it possible to force this in tandem? Ie. when one of the keys
has to be quoted, the other is always quoted also? Because Iâd
hate to see this:
wanted: elbow
found: 'elbow '
For simple cases like this one itâs livable, but if
* Ovid [EMAIL PROTECTED] [2007-09-03 21:20]:
If string data was *always* quoted and numeric data never was
(assuming it's really numeric),
Fine with me.
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
--- Michael G Schwern [EMAIL PROTECTED] wrote:
Ovid wrote:
After doing a bit of thinking about this and chatting with Andy
Armstrong about this, I've realized that much of the current
thought
about the TAP diagnostics is wrong. We already have much of what
we
want in the TAP line
On 9/1/07, Fergal Daly [EMAIL PROTECTED] wrote:
On 30/08/07, Ovid [EMAIL PROTECTED] wrote:
After doing a bit of thinking about this and chatting with Andy
Armstrong about this, I've realized that much of the current thought
about the TAP diagnostics is wrong. We already have much of what
demerphq wrote:
On 9/1/07, Fergal Daly [EMAIL PROTECTED] wrote:
On a tangent, I think using quotes is important otherwise you end up output
like
wanted: elbow
found: elbow
when what you really needed was
wanted: 'elbow'
found: 'elbow '
No need to quote
On 9/1/07, Michael G Schwern [EMAIL PROTECTED] wrote:
demerphq wrote:
On 9/1/07, Fergal Daly [EMAIL PROTECTED] wrote:
On a tangent, I think using quotes is important otherwise you end up
output like
wanted: elbow
found: elbow
when what you really needed was
# from demerphq
# on Saturday 01 September 2007 07:59 am:
Could this be a reason NOT to emit a YAML stream?
Not particularly, why do you ask?
Cause id hate to see all this work done and then find out that its
less than it could be because YAML in the end doesnt meet the
requirements. If it
--- Adrian Howard [EMAIL PROTECTED] wrote:
Minimum required:
wanted
found
line
file
description
I'm uncomfortable with any minimum to be honest. I'd be happier
with recommended.
For example I write customer-facing tests that read like
Ovid wrote:
After doing a bit of thinking about this and chatting with Andy
Armstrong about this, I've realized that much of the current thought
about the TAP diagnostics is wrong. We already have much of what we
want in the TAP line above the diagnostics so there's no need to be
redundant.
On 28 Aug 2007, at 11:26, Ovid wrote:
[snip]
If we can't come to a consensus, I'll plow ahead regardless.
Go plough my friend :-)
As usual,
this means I might create something that no one likes. What I'd
prefer
to define is the *minimum* required keys in the YAML diagnostics and
Hi all,
I've just started hacking together TAP::Diagnostics. This would be a
simple helper module that allows test authors to spit out the YAMLish
diagnostics envisioned for future versions of TAP. I have some
specific ideas on how to make this work, but we need to agree on the
format. For
26 matches
Mail list logo
