[Pdl-devel] RESEND: Change in xvals/yvals/zvals behavior

2024-01-28 Thread Diab Jerius via pdl-devel
[Apologies, the last email was sent from the wrong email address. PLEASE disregard] Hey folks, I’d like to submit some sort of fix to the change in behavior I’ve noted at the bottom of this issue, https://github.com/PDLPorters/pdl/issues/330 namely that [xyz]vals return a double regardless

Re: [Pdl-devel] Ubuntu/debian PDL packages & pgplot

2021-08-16 Thread Diab Jerius via pdl-devel
cement for P:G:PGPLOT. My feeling is that Craig’s work on it was so good that very little if anything will actually be needed. Best regards, Ed *From: *Diab Jerius <mailto:djer...@cfa.harvard.edu> *Sent: *16 August 2021 17:10 *To: *Karl Glazebrook <mailto:kglazebr...@swin.edu.au> *Cc:

Re: [Pdl-devel] Ubuntu/debian PDL packages & pgplot

2021-08-16 Thread Diab Jerius via pdl-devel
Here's an alternative (more general issue of PGPLOT support, not necessarily to solve the Ubuntu/Debian problem). There's an autotooled version of PGPLOT here: https://github.com/djerius/pgplot-autotool 1. Create an Alien::PGPLOT module 2. Make the CPAN PGPLOT package depend on that, 3. Move P

Re: [Pdl-devel] PDL maintainer/co-maintainer

2019-07-22 Thread Diab Jerius
Could you include ExtUtils::F77 in the process? > > Best regards, > Ed > > *From:* Chris Marshall > *Sent:* Monday, July 22, 2019 3:57 PM > *To:* Ed . ; pdl-devel@lists.sourceforge.net > *Cc:* Diab Jerius > *Subject:* PDL maintainer/co-maintainer > > Ed/Diab- > >

[Pdl-devel] RFC: Improving documentation

2019-06-11 Thread Diab Jerius
I recognize how hard documentation is to write, and I'm grateful that PDL has so much of it. However, there is room for improvement. The following comments are intended as an objective critique and to start a discussion which can lead to cohesive design and documentation standards. The current d

Re: [Pdl-devel] PDL release; I'm volunteering.

2019-06-11 Thread Diab Jerius
d mandating a clean core namespace so that we don't have collisions. > > -Original Message- > From: Diab Jerius > Sent: Thursday, May 23, 2019 10:32 PM > To: pdl-devel@lists.sourceforge.net ; Ed . > Subject: Re: [Pdl-devel] PDL release; I'm volunteering. > &g

[Pdl-devel] Fwd: Fwd: PDL release; I'm volunteering.

2019-06-11 Thread Diab Jerius
-- Forwarded message - From: Diab Jerius Date: Tue, Jun 11, 2019 at 9:51 AM Subject: Re: [Pdl-devel] Fwd: PDL release; I'm volunteering. To: Chris Marshall Sorry for the radio silence! We've had a wet spring in the Boston area and suddenly got nice weekend weather, w

Re: [Pdl-devel] PDL release; I'm volunteering.

2019-05-23 Thread Diab Jerius
On Thu, May 23, 2019 at 1:27 PM Diab Jerius wrote: > My philosophy is that the only things that should be methods are those > that require knowledge of the private innards of a piddle, or that are > required for implementing overloaded operators (useful for subclassing > PDL. I

Re: [Pdl-devel] PDL release; I'm volunteering.

2019-05-23 Thread Diab Jerius
of approaches that can work (this is Perl after all). Particularly when we're dealing with a group of users that might not eat objects for breakfast. > What would your list of PDL* methods be? I'll have to think about that a bit. > > -Original Message- > From: Dia

[Pdl-devel] Fwd: PDL release; I'm volunteering.

2019-05-23 Thread Diab Jerius
-- Forwarded message - From: Diab Jerius Date: Thu, May 23, 2019 at 12:40 PM Subject: Re: [Pdl-devel] PDL release; I'm volunteering. To: Ed . Ed, Thanks for your reply On Thu, May 23, 2019 at 11:37 AM Ed . wrote: > > Hi Diab, > > It seems you got the same

Re: [Pdl-devel] PDL release; I'm volunteering.

2019-05-23 Thread Diab Jerius
any response to my offer, or if I've unknowingly tread on some toes, please let me know (or more references are required) please let me know! Thanks, Diab On Thu, May 9, 2019 at 2:38 PM Diab Jerius wrote: > > Hi, > > I'm willing to marshal the next release of PDL.[

[Pdl-devel] PDL release; I'm volunteering.

2019-05-09 Thread Diab Jerius
Hi, I'm willing to marshal the next release of PDL.[0] PDL needs to keep going while its future successor is developed and planned.[1] While PDLA is promising, it's not a simple drop-in replacement, and perhaps shouldn't be. To move PDL into its proper place in the Perl ecosystem[2] requires a l

Re: [Pdl-devel] RFC: Coordinated masking of piddles.

2016-10-28 Thread Diab Jerius
PDLx::Mask is now up on CPAN. A bit of code churn going on, the API should be fairly stable. On Mon, Oct 24, 2016 at 4:09 PM, Diab Jerius wrote: > I've developed this into the modules PDLx::Mask and PDLx::MaskedData. > > For now, they're just up at github & bitbucket:

Re: [Pdl-devel] Subclassing PDL made easier with PDLx::DetachedObject

2016-10-26 Thread Diab Jerius
gt;>> Thanks for the additional clarification for context---what a mess! >>> >>> From your example, it seems that the current PDL approach for OO via >>> "has-a" doesn't work but my question is what method would work? Is there an >>> example of

Re: [Pdl-devel] Subclassing PDL made easier with PDLx::DetachedObject

2016-10-26 Thread Diab Jerius
> "has-a" doesn't work but my question is what method would work? Is there an >> example of an OO language or framework that can be shown to work for this >> type of problem? Is the problem with PDL, perl5, both, neither? >> >> --Chris >> >> &g

Re: [Pdl-devel] RFC: Coordinated masking of piddles.

2016-10-24 Thread Diab Jerius
https://github.com/djerius/PDLx-DetachedObject Comments appreciated. Diab On Tue, Oct 11, 2016 at 11:26 AM, Diab Jerius wrote: > Masking out elements of piddles is something that PDL has supported > for a long time via bad values. This works well if all operations > performed on the piddl

Re: [Pdl-devel] Subclassing PDL made easier with PDLx::DetachedObject

2016-10-24 Thread Diab Jerius
On Mon, Oct 24, 2016 at 12:43 PM, Diab Jerius wrote: > initialize() currently must assume that object construction can be > done without any arguments to the constructor. That's inappropriate > in some instances (as described above). And once more, to clarify... initialize() is

Re: [Pdl-devel] Subclassing PDL made easier with PDLx::DetachedObject

2016-10-24 Thread Diab Jerius
On Mon, Oct 24, 2016 at 12:43 PM, Diab Jerius wrote: > initialize() currently must assume that object construction can be > done without any arguments to the constructor. I shouldn't have used the word "currently", as that implies there's a way of changing its behavior,

Re: [Pdl-devel] Subclassing PDL made easier with PDLx::DetachedObject

2016-10-24 Thread Diab Jerius
described above). > However, sight unseen, maybe using a the PDL > attribute as a code ref + closure might be a way to > work around the difficulty? This might work if initialize() were called more consistently. > > I definitely would like to see PDL and PDL::NextGen > be interop

[Pdl-devel] Subclassing PDL made easier with PDLx::DetachedObject

2016-10-21 Thread Diab Jerius
I've been having lots of fun lately creating complex classes which inherit from PDL. Unfortunately, when PDL creates objects on the fly, e.g. when it needs to store the result of an operation: $mpdl = MyPDL->new; $npdl = $mpdl + 1; # $npdl will be of class MyPDL it can't pass along any addit

[Pdl-devel] RFC: Coordinated masking of piddles.

2016-10-11 Thread Diab Jerius
Masking out elements of piddles is something that PDL has supported for a long time via bad values. This works well if all operations performed on the piddle respect bad values, and it doesn't quite matter that you may be overwriting a value with the bad value (at worst, you keep a copy of the ori

Re: [Pdl-devel] [pdl:bugs] #427 PDL->null->copy returns an empty (not null) piddle

2016-10-11 Thread Diab Jerius
above...) > > Seems a simple change but I don't know enough about > the threadI and sever operations on Null piddles to > apply something for the release I'm planning to push > tomorrow AM. > > Cheers, > Chris > > > > > > > On 10/7/2016

Re: [Pdl-devel] [pdl:bugs] #427 PDL->null->copy returns an empty (not null) piddle

2016-10-07 Thread Diab Jerius
e specialness of > Null piddles and trying to do the right (wrong) thing could be more friendly. > API discussion is needed. Please continue discussion on the PDL mailing > lists. > > > > --- > > ** [bugs:#427] PDL->null->copy returns an empty (not null) piddle** >