yes, meaningful error messages with the code line in the user's code and
not just pdl internals would be really appreciated.

Ingo

On 12/06/2013 04:29 PM, Piero Ranalli wrote:
> Hi
>
> reading the following line from Ingo:
>
>> Far less important but still, the barf on multielement piddles!
> I remembered another thing that maybe could be improved.  When there's
> an error message, it points to within the PDL source code, as in the
> following one-liner:
>
> piero$ perl -MPDL -E '$q=sequence 10; say $q->at(11);'
> Position out of range at Basic/Core/Core.pm.PL (i.e. PDL::Core.pm) line 3300.
>
> I'd really like the message to point at my code, instead of PDL's.
> Would it be difficult for PDL to use Carp (or any similar approach)?
>
>
> regards,
> Piero
>
> _______________________________________________
> Perldl mailing list
> [email protected]
> http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
>


_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl

Reply via email to