[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
Thanks!
Regards,
Luis
On Sun, Jan 28, 2024 at 04:25:27PM +, Ed . wrote:
> Hi Luis,
>
> This is a long-standing issue in PDL. If your code creates a
> PDL::somefunction, there is indeed a risk that someone else’s code also makes
> a PDL::somefunction, and there will be a problem. Using
Hi Luis,
This is a long-standing issue in PDL. If your code creates a PDL::somefunction,
there is indeed a risk that someone else’s code also makes a PDL::somefunction,
and there will be a problem. Using “warnings” in both modules will at least
tell you it happened.
A way to dodge this is to
Hi,
It is sometimes convenient to call my own functions that operate on ndarrays
using the object notation: $ndarray->somefunction. A simple way to do
it is to define the function within the PDL name space as in
sub PDL::somefunction($self,...){...}
Is there a better way? Adding functions to a
