Re: new Stream Test::Simple question, XS requirement

2015-04-25 Thread Chad Granum
Just to also be clear. My alternate implementation would be a fallback. If scalar::util works it uses it, if not it falls back to a slightly different system. The switch would happen when Context.pm is loaded. So even if the fallback is slightly slower, few if any systems would ever experience it.

Re: new Stream Test::Simple question, XS requirement

2015-04-25 Thread Chad Granum
I am not sure it is entirely my decision. If it is entirely my decision than this is it: Must have a working scalar::util::weaken to use the new Test::Simple. The Test-Simple dist itself will not require a c compiler to install, as in no xs is included in the dist. A Test-Simple-XS dist may be crea

Re: new Stream Test::Simple question, XS requirement

2015-04-25 Thread bulk88
Chad Granum wrote: I have no objections to having OPTIONAL XS available to speed things up for people who want it. However I will not accept making XS a requirement. I thought that since Scalar::Util::weaken was in core that there would be no issues using it in a core module. Core includes XS

Re: new Stream Test::Simple question, XS requirement

2015-04-25 Thread Ricardo Signes
* bulk88 [2015-04-25T17:57:19] > Since Test::Stream::Context's core design uses weaken() everywhere, that > means new Test::Simple always requires XS building (for Scalar::Util), which > means it will never run on miniperl, and hence, new Test::Simple will never > be in Perl core, is my understand

Re: new Stream Test::Simple question, XS requirement

2015-04-25 Thread Leon Timmermans
On Sat, Apr 25, 2015 at 11:57 PM, bulk88 wrote: > Since Test::Stream::Context's core design uses weaken() everywhere, that > means new Test::Simple always requires XS building (for Scalar::Util), > which means it will never run on miniperl, and hence, new Test::Simple will > never be in Perl core

Re: new Stream Test::Simple question, XS requirement

2015-04-25 Thread James E Keenan
On 04/25/2015 05:57 PM, bulk88 wrote: Since Test::Stream::Context's core design uses weaken() everywhere, that means new Test::Simple always requires XS building (for Scalar::Util), which means it will never run on miniperl, and hence, new Test::Simple will never be in Perl core, is my understand

Re: new Stream Test::Simple question, XS requirement

2015-04-25 Thread Chad Granum
I have no objections to having OPTIONAL XS available to speed things up for people who want it. However I will not accept making XS a requirement. I thought that since Scalar::Util::weaken was in core that there would be no issues using it in a core module. If using weaken makes Test-Simple non-cor

new Stream Test::Simple question, XS requirement

2015-04-25 Thread bulk88
Since Test::Stream::Context's core design uses weaken() everywhere, that means new Test::Simple always requires XS building (for Scalar::Util), which means it will never run on miniperl, and hence, new Test::Simple will never be in Perl core, is my understanding correct? I am asking this since

Re: Communicating between processes in test suite run

2015-04-25 Thread Cosimo Streppone
Il 24/04/2015 18:12, Michael Kiwala ha scritto: On Thu, Apr 23, 2015 at 2:53 PM, Tim Bunce mailto:tim.bu...@pobox.com>> wrote: That approach only applies to your perl statsd, right? For the nodejs or C statsd's you don't have an easy[*] a way to find the port. I was about to suggest ru