> At some point, the cookbook and possibly the tutorials
> should be bundled into CPAN distributions. Perhaps POE::Tutorials
> or POE::Examples
I'm almost tempted to suggest that should be left to each distro...
in RH one often finds packages like -doc containing all that stuff.
> At some point, the cookbook and possibly the tutorials
> should be bundled into CPAN distributions. Perhaps POE::Tutorials
> or POE::Examples
I'm almost tempted to suggest that should be left to each distro...
in RH one often finds packages like -doc containing all that stuff.
> At some point, the cookbook and possibly the tutorials
> should be bundled into CPAN distributions. Perhaps POE::Tutorials
> or POE::Examples
I'm almost tempted to suggest that should be left to each distro...
in RH one often finds packages like -doc containing all that stuff.
Randal L. Schwartz
> Don't remove all examples from the distro. At 30K feet, they were
> very helpful for me while I was trying to write code, but couldn't
> get
> to the website. Or maybe make a simple "one-stop-download" link on
> the website.
they can at least be packaged separately. in fact
> "Rocco" == Rocco Caputo <[EMAIL PROTECTED]> writes:
Rocco> Added to the plan:
Rocco> At some point, the cookbook and possibly the tutorials should be
Rocco> bundled into CPAN distributions. Perhaps POE::Tutorials or
Rocco> POE::Examples, so the low-tech and high-altitude crowds can a
On Sun, Feb 22, 2004 at 04:49:53AM -0800, Randal L. Schwartz wrote:
> > "Rocco" == Rocco Caputo <[EMAIL PROTECTED]> writes:
>
> Rocco> POE still ships with about 200K of samples, and it will continue to
> Rocco> until they're replaced by cookbook recipes or tutorials. The plans
> Rocco> have
> "Rocco" == Rocco Caputo <[EMAIL PROTECTED]> writes:
Rocco> POE still ships with about 200K of samples, and it will continue to
Rocco> until they're replaced by cookbook recipes or tutorials. The plans
Rocco> have been on display for months at
Rocco> http://poe.perl.org/?POE_RFCs/Deprecate_S
On Sat, Feb 21, 2004 at 01:13:30AM -0500, sungo wrote:
> On (02/07 15:53), Rocco Caputo wrote:
>
> > I think the tests should be generated at "make test" time. We get a
> > smaller distribution this way.
>
> you've never been terribly concerned about a really small distribution
> before. we've s
On (02/07 15:53), Rocco Caputo wrote:
> I think the tests should be generated at "make test" time. We get a
> smaller distribution this way.
you've never been terribly concerned about a really small distribution
before. we've shipped 10K of examples until really recently. i'd much
rather ship 10
This thread has stalled. I made more revisions to
http://poe.perl.org/?POE_RFCs/Test_Reforms while waiting for feedback.
--
Rocco Caputo - [EMAIL PROTECTED] - http://poe.perl.org/
On Fri, Feb 06, 2004 at 11:57:26PM -0500, sungo wrote:
> On (02/04 04:14), Rocco Caputo wrote:
>
> > Thanks for the reply. http://poe.perl.org/?POE_RFCs/Test_Reforms has
> > been harshly (and incompletely, but it's like 03:00 here) revised based
For perspective:
The goal of updating POE's test
On (02/04 04:14), Rocco Caputo wrote:
> Thanks for the reply. http://poe.perl.org/?POE_RFCs/Test_Reforms has
> been harshly (and incompletely, but it's like 03:00 here) revised based
so, we've gone from our current test suite which is not complete but
workable to a proposed test suite which invo
On (02/04 04:14), Rocco Caputo wrote:
> So in practice the wiki's a flop.
i don't think i'd say that. the Cookbook alone makes it a success.
but the wiki is not a project management or team collaboration tool. its
just a web site. esp since watching the wiki for new content is an
active ende
On Tue, Feb 03, 2004 at 04:04:10PM -0500, Sean Egan wrote:
>
> I read the page and I like the idea of a plan for standardized
> test. Howver, I am a little concerned with some parts of the plan.
>
> The "unit tests" sound good but POE is a whole environment. So
> having unit tests are a good thin
I read the page and I like the idea of a plan for standardized
test. Howver, I am a little concerned with some parts of the plan.
The "unit tests" sound good but POE is a whole environment. So
having unit tests are a good thing for those parts that can
be isolated, but overall will have limited i
Rocco Caputo wrote:
I gave it a shot. Devel::Cover has come a long way since I last looked
at it. It only introduces failures in three of the tests.
The results are temporarily available at http://nopaste.snit.ch:8001/541
Yep, it sure has. You want to generate the HTML report next, which wil
On Tue, Feb 03, 2004 at 10:13:04AM +1300, Sam Vilain wrote:
> Rocco Caputo wrote:
>
> >Tests are a vital part of the POE project. Its current tests succeed at
> >covering about 70% of POE's its instrumentable breakpoints, but they do
> >so without any coherent plan.
> >
> Have you tried running t
Rocco Caputo wrote:
Tests are a vital part of the POE project. Its current tests succeed at
covering about 70% of POE's its instrumentable breakpoints, but they do
so without any coherent plan.
Have you tried running the test suite with Devel::Cover ? It replaces
the Perl_runops() loop with
18 matches
Mail list logo
