-
Notifications
You must be signed in to change notification settings - Fork 559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BBC: Blead Breaks PDL #22354
Comments
Bisecting (which took exactly 1 hour on my fastest machine) with the following invocation:
... pointed to 42cf752
@Leont, can you take a look? Thanks. |
That is quite a surprise. It seems PDL has its own typemap evaluator that will need to be adapted to this change. |
Notified upstream of problem: PDLPorters/pdl#487 |
Fortunately, that code in PDL's Basic::Gen::PP was developed relatively recently ...
... so hopefully @mohawk2 will be able to help you out on this. |
@Leont Can you guide me on what this change means for PDL? Are you asking me to change the code? Will it work on older EU:PXS? Whose life is better as a result of this "alignment"? When is the new EU:PXS going to be released on CPAN? I added the |
@Leont To cut to the chase: please revert your change, and find another way if you must to achieve what you were trying to do. Thanks. |
Absolutely. Even if this change is reverted you should change the code (but in a different way); it's broken for output maps because those are already using
I'm not sure exactly what you're asking here, but yes. It would break any typemap abusing quotes to get out of the string, but there's only one typemap on all of CPAN that does such a thing and it's easily fixed.
People who actually have to write typemaps. Previously, unescaped double quotes would break in highly confusing ways in input maps if you ever used them. So one would have to write stuff like: if (SvIV($arg) < 0))
croak(\"Something is wrong\"); It's one of those things that makes writing typemaps really confusing and counter-intuitive. After this change you can just do: if (SvIV($arg) < 0))
croak("Something is wrong"); It's extra confusing because output templates have always used the latter syntax.
Not sure. Would you want me to do a trial release now? |
@Leont Are you happy to make the PR to PDL that is backwards-compatible with both currently-released and your updated version of EU:PXS? If there's backward compatibility, then EU:PXS's sometimes-rather-slow release cycle stops being a problem. I don't see that a trial release per se will help with this overall issue, but am open to being wrong. |
Yeah I will do that. |
I ran into this issue today and can confirm that with the fix @Leont suggested in PDLPorters/pdl#487 (comment), PDL tests pass with Perl 5.41.3, and also with my system Perl (5.34). |
If it works with existing Perls and existing EU:PXS (which the CI will show), yes, please do. |
PDL 2.090 has been released, with @HaraldJoerg's update within it. Please check this against the latest EU:PXS. |
PDL 2.090 is doing well on CPANtesters: http://fast-matrix.cpantesters.org/?dist=PDL. I believe we should be able to close this ticket after a couple more days of testing. |
This is a bug report for perl from "Carlos Guevara" carlos@carlosguevara.com,
generated with the help of perlbug 1.43 running under perl 5.41.1.
BBC: Blead Breaks PDL
Please see http://fast-matrix.cpantesters.org/?dist=PDL%202.089
Flags
Perl configuration
The text was updated successfully, but these errors were encountered: