Re: [Pdl-devel] PDL 2.075 released

2022-02-26 Thread Ed .
: Ingo Schmid<mailto:ingo...@gmx.at>; David Mertens<mailto:dcmertens.p...@gmail.com> Cc: pdl-devel<mailto:pdl-devel@lists.sourceforge.net> Subject: RE: [Pdl-devel] PDL 2.075 released Hi Ingo, The specific case of a single-element ndarray which has a badvalue returning true

Re: [Pdl-devel] PDL 2.075 released

2022-02-25 Thread David Mertens
documented as returning Perl scalars, and I was extremely surprised > when I discovered it then did so. > > > > Best regards, > > Ed > > > > *From: *David Mertens > *Sent: *24 February 2022 15:53 > *To: *Ingo Schmid > *Cc: *pdl-devel > *Subject: *Re:

Re: [Pdl-devel] PDL 2.075 released

2022-02-25 Thread Ed .
mailto:ej...@hotmail.com>; David Mertens<mailto:dcmertens.p...@gmail.com> Cc: pdl-devel<mailto:pdl-devel@lists.sourceforge.net> Subject: Re: [Pdl-devel] PDL 2.075 released Hi Ed, I do not mind the behaviour as such but rather the fact that it changed. That breaks previous code in non-ob

Re: [Pdl-devel] PDL 2.075 released

2022-02-25 Thread Ingo Schmid
February 2022 19:08 > *To: *Ed . <mailto:ej...@hotmail.com>; David Mertens > <mailto:dcmertens.p...@gmail.com> > *Cc: *pdl-devel <mailto:pdl-devel@lists.sourceforge.net> > *Subject: *Re: [Pdl-devel] PDL 2.075 released > >   > > Ed & David, > > I

Re: [Pdl-devel] PDL 2.075 released

2022-02-24 Thread Ed .
.sourceforge.net<mailto:pdl-devel@lists.sourceforge.net> Subject: RE: [Pdl-devel] PDL 2.075 released Hi Ingo, I believe you didn’t run your code before emailing it, because $p isn’t defined. Also, I hope the real code doesn’t have an isempty followed by a Boolean check on ->nelem, because

Re: [Pdl-devel] PDL 2.075 released

2022-02-24 Thread Ed .
ail.com>; David Mertens<mailto:dcmertens.p...@gmail.com> Cc: pdl-devel<mailto:pdl-devel@lists.sourceforge.net> Subject: Re: [Pdl-devel] PDL 2.075 released Ed & David, I stumbled across the problem because of this behaviour: pdl> p max pdl[] BAD which does not expand to 0 a

Re: [Pdl-devel] PDL 2.075 released

2022-02-24 Thread Ingo Schmid
re never documented as returning Perl scalars, and I was extremely > surprised when I discovered it then did so. > >   > > Best regards, > > Ed > >   > > *From: *David Mertens <mailto:dcmertens.p...@gmail.com> > *Sent: *24 February 2022 15:53 > *To: *Ingo Sc

Re: [Pdl-devel] PDL 2.075 released

2022-02-24 Thread Ed .
ts.sourceforge.net> Subject: RE: [Pdl-devel] PDL 2.075 released Hi Ingo, I believe you didn’t run your code before emailing it, because $p isn’t defined. Also, I hope the real code doesn’t have an isempty followed by a Boolean check on ->nelem, because isempty is literally implemented as nel

Re: [Pdl-devel] PDL 2.075 released

2022-02-24 Thread Ed .
sourceforge.net> Subject: Re: [Pdl-devel] PDL 2.075 released HI Ed, here's some feedback to the new release. Thank you for your tireless efforts! I experience errors in previously working code, at least in 2.074 and 2.075. $r and $i are piddles, as are $empty_lines and $vlines. These lines (6

Re: [Pdl-devel] PDL 2.075 released

2022-02-24 Thread Ed .
et> Subject: Re: [Pdl-devel] PDL 2.075 released To follow-up on max/min being piddles, this broke some of my tests in PDL::Parallel::threads. Specifically croak-in-boolean-context is now easily triggered where it used to be safe: if ($data->max < 40) { # croaks: piddle in boolean context

Re: [Pdl-devel] PDL 2.075 released

2022-02-24 Thread David Mertens
To follow-up on max/min being piddles, this broke some of my tests in PDL::Parallel::threads. Specifically croak-in-boolean-context is now easily triggered where it used to be safe: if ($data->max < 40) { # croaks: piddle in boolean context } Was this use case considered and discussed?

Re: [Pdl-devel] PDL 2.075 released

2022-02-24 Thread Ingo Schmid
HI Ed, here's some feedback to the new release. Thank you for your tireless efforts! I experience errors in previously working code, at least in 2.074 and 2.075. $r and $i are piddles, as are $empty_lines and $vlines. These lines (67 #!perl use PDL; use PDL::NiceSlice; use 5.10.0; use strict