Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-11 Thread Jens Rehsack
Am 04.06.2014 um 07:00 schrieb Jens Rehsack rehs...@gmail.com: Am 04.06.2014 um 04:32 schrieb David Golden x...@xdg.me: On Tue, Jun 3, 2014 at 1:35 AM, Jens Rehsack rehs...@gmail.com wrote: 1) compiler cannot create executables 2) compiler works, but no perl headers 3) compiler does,

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-03 Thread Peter Rabbitson
On Sun, Jun 01, 2014 at 08:15:20PM +0200, Jens Rehsack wrote: Am 01.06.2014 um 20:09 schrieb Peter Rabbitson rab...@rabbit.us: On Sun, Jun 01, 2014 at 05:59:16PM +0200, Jens Rehsack wrote: Am 01.06.2014 um 15:03 schrieb David Golden x...@xdg.me: The only thing specified in the

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-03 Thread Peter Rabbitson
On Sun, Jun 01, 2014 at 05:59:16PM +0200, Jens Rehsack wrote: Am 01.06.2014 um 15:03 schrieb David Golden x...@xdg.me: The only thing specified in the lancaster consensus is what must happen if that command-line argument is true. I think making a distinction between 0 and undefined

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-03 Thread David Golden
On Tue, Jun 3, 2014 at 1:35 AM, Jens Rehsack rehs...@gmail.com wrote: 1) compiler cannot create executables 2) compiler works, but no perl headers 3) compiler does, but shared library building fails (that is fragile and minor modifications at the system causes that process to fail) These

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-03 Thread Jens Rehsack
Am 04.06.2014 um 04:32 schrieb David Golden x...@xdg.me: On Tue, Jun 3, 2014 at 1:35 AM, Jens Rehsack rehs...@gmail.com wrote: 1) compiler cannot create executables 2) compiler works, but no perl headers 3) compiler does, but shared library building fails (that is fragile and minor

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-02 Thread Jens Rehsack
Am 02.06.2014 um 13:34 schrieb David Golden x...@xdg.me: On Mon, Jun 2, 2014 at 7:28 AM, Jens Rehsack rehs...@gmail.com wrote: Others (eg. packagers) have always a compiler and want benefit from XS when available and what is more important: if the DEVELOPER MODE FLAGS IS ON, they want to

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-02 Thread David Golden
On Mon, Jun 2, 2014 at 7:53 AM, Jens Rehsack rehs...@gmail.com wrote: Am 02.06.2014 um 13:34 schrieb David Golden x...@xdg.me: On Mon, Jun 2, 2014 at 7:28 AM, Jens Rehsack rehs...@gmail.com wrote: Others (eg. packagers) have always a compiler and want benefit from XS when available and what

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-02 Thread David Golden
On Mon, Jun 2, 2014 at 9:22 AM, Jens Rehsack rehs...@gmail.com wrote: Web-Search for CPAN Testers magic strings doesn't provide suitable results - is there a list of those magic results? http://wiki.cpantesters.org/wiki/CPANAuthorNotes If I would know what is expected, I will make

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-02 Thread Jens Rehsack
Am 02.06.2014 um 16:05 schrieb David Golden x...@xdg.me: On Mon, Jun 2, 2014 at 9:22 AM, Jens Rehsack rehs...@gmail.com wrote: Web-Search for CPAN Testers magic strings doesn't provide suitable results - is there a list of those magic results?

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-02 Thread Aristotle Pagaltzis
Hi Jens, * Jens Rehsack rehs...@gmail.com [2014-06-02 13:30]: * Karen Etheridge p...@froods.org [2014-06-02 01:30]: I'm wondering why it isn't always possible to split a dist into two implementations, one PP and the other with XS optimizations. If the dist simply cannot be implemented

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-02 Thread David Golden
On Mon, Jun 2, 2014 at 7:28 PM, Aristotle Pagaltzis pagalt...@gmx.de wrote: If I have my system set up to support XS then I want it to use XS, and if for some reason it can’t, then there is a bug somewhere that needs to be fixed, so I do *not* want it to silently give me the PP version and

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-02 Thread Jens Rehsack
Am 03.06.2014 um 01:28 schrieb Aristotle Pagaltzis pagalt...@gmx.de: * Karen Etheridge p...@froods.org [2014-06-02 01:30]: I do not see any gain in specifying give me XS or give me death. This I find easy to see, at least if we are talking of the general case: If I have my system set up

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-02 Thread Jens Rehsack
Am 03.06.2014 um 01:42 schrieb David Golden x...@xdg.me: On Mon, Jun 2, 2014 at 7:28 PM, Aristotle Pagaltzis pagalt...@gmx.de wrote: If I have my system set up to support XS then I want it to use XS, and if for some reason it can’t, then there is a bug somewhere that needs to be fixed, so I

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-01 Thread David Golden
The only thing specified in the lancaster consensus is what must happen if that command-line argument is true. I think making a distinction between 0 and undefined will be surprising to people and I would recommend against it. On Sun, Jun 1, 2014 at 7:19 AM, Jens Rehsack rehs...@gmail.com

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-01 Thread Jens Rehsack
Am 01.06.2014 um 15:03 schrieb David Golden x...@xdg.me: The only thing specified in the lancaster consensus is what must happen if that command-line argument is true. I think making a distinction between 0 and undefined will be surprising to people and I would recommend against it. Given

Re: Lancaster Consensus, deal with PUREPERL_ONLY=0

2014-06-01 Thread Jens Rehsack
Am 01.06.2014 um 20:09 schrieb Peter Rabbitson rab...@rabbit.us: On Sun, Jun 01, 2014 at 05:59:16PM +0200, Jens Rehsack wrote: Am 01.06.2014 um 15:03 schrieb David Golden x...@xdg.me: The only thing specified in the lancaster consensus is what must happen if that command-line argument is