mauke
mauke
I get ``` hello world ``` as expected.
That is working as expected. The whole point of the `package Foo { ... }` syntax is that everything outside the braces is not part of the `Foo` package.
Bisect says: 386907f061c1812ecaa5f3c88d9f729828408097 is the first bad commit ``` commit 386907f061c1812ecaa5f3c88d9f729828408097 Author: Tony Cook Date: Thu Sep 14 10:37:42 2023 +1000 Revert "[perl #89544] Non-eval closures don’t need CvOUTSIDE" But...
I've been thinking about this. I now think your example: ```perl use strict; package DB { sub myeval { eval shift or die } } my $y = 1; #...
May I suggest replacing the test file by this? ```diff diff --git t/test_pl/display_ro.t t/test_pl/display_ro.t new file mode 100644 index 0000000000..49e4c5b6c5 --- /dev/null +++ t/test_pl/display_ro.t @@ -0,0 +1,13 @@ +#!./perl +...
To make the version tests pass, you'll need to bump the version of `POSIX.pm`. You should also document the new `atexit` in `POSIX.pod`.
> I can see the use of this, but I'm not sure if POSIX is the right place for it. Why not? It seems like the natural place to me:...
Probably the same root cause: ``` $ ./perl -Ilib -e 'use Tie::RefHash (); Tie::RefHash::refaddr(0)' Segmentation fault ```
... which in turn reduces to: ``` $ perl -e 'sub { goto &builtin::refaddr; }->(0)' Segmentation fault ```
I've sync'd Tie::RefHash into core. Hopefully the workaround there will fix the Tie::RefHash::Weak errors. Once that is confirmed, we can close this issue, I think. For the underlying root cause...