Whether or not the code makes sense or not, you shouldn't ever get a segfault. I just checked with bleadperl and it doesn't segfault there so (unless something changes to make it come back again and there isn't already a test for it) it will be fine in 5.10. It does however appear to still do this in the maintenance branch so it would be worth checking whether this had already been reported and if not reporting it via perlbug. It also appears that this behaviour has existed at least as far back as 5.00404 which is the oldest version I have to test with.
Update: Interestingly it does do it with bleadperl, it just doesn't seem to do it with the eval present:
[jonathan@orpheus perl-current]$ ./perl -e'BEGIN { *@=1; }' Segmentation fault (core dumped) [jonathan@orpheus perl-current]$ ./perl -e'BEGIN { *@=1; eval '' }' [jonathan@orpheus perl-current]$
/J\
In reply to Re: eval segfaults when $@ isn't writable
by gellyfish
in thread eval segfaults when $@ isn't writable
by Hue-Bond
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |