On 3/1/07, David Golden [EMAIL PROTECTED] wrote:
I've had some requests for a mechanism for module authors to indicate
whether or not they want to be copied on module test emails generated
by CPAN::Reporter (particularly for passing reports). This seems like
the kind of thing that should go in
Hello,
I have just finished a module I need at a gig with a client. The
module is called Test::Timer, it resembles, Test::Benchmark a lot,
apart from it is much simpler.
It exports a single method: time_ok
Which takes a body of code, a threshold and a name;
time_ok( sub {
On 3/1/07, David Golden [EMAIL PROTECTED] wrote:
I've had some requests for a mechanism for module authors to indicate
whether or not they want to be copied on module test emails generated
by CPAN::Reporter (particularly for passing reports). This seems like
the kind of thing that should go in
On 3/1/07, Adriano Ferreira [EMAIL PROTECTED] wrote:
My suggestion would be to have a section 'hints' in META.yml (that
I think that's an excellent name for the section I proposed.
Of course, we would like to see all the variants we grow used to, like
cc_author: no
cc_author: yes
I've had some requests for a mechanism for module authors to indicate
whether or not they want to be copied on module test emails generated
by CPAN::Reporter (particularly for passing reports). This seems like
the kind of thing that should go in the module META.yml.
Is there a de facto standard
David Golden writes:
Is there a de facto standard for custom extensions to META.yml? (I
didn't see one in the spec.) An example might be fields beginning
with a capital letter or X-foo style extensions. E.g.
X-cc-author: no
Does putting X- in front of such fields really help? X- isn't
* Smylers [EMAIL PROTECTED] [2007-03-01 21:45]:
Can't we just start using cc-author as a field, then if it
takes off get it blessed as part of the official spec?
Then how do you tell whether `bastract` is a typo or extension
field?
I think adding a `hints` field which is a hash of hashes,
I'm in the process of implementing a large scale central syslog
architecture based on syslog-ng and POE. syslog-ng buys me compliance
while I finish building my custom correlation engine with POE.
I wanted a way to deal with syslog messages as they came in from the
network, as well as messages
Following David Goldens' observations, Adriano Ferreira wrote:
This way, the section to be added to META.yml would be
hints:
test_reporter:
cc_author: no
This seems a very pragmatic solution to a problem, however given recent
posts, it seems to be a solution in search of approval - is
