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
perl -s does not respect read-onlyness, can cause segfaults #13317
Comments
From @HugmeirCreated by @Hugmeir$ perl -E 'say $] = 10' Also, there's a 5.10 regression here: Rather than fixing those, how about we deprecate -s? Perl Info
|
From @cpansproutOn Sat Sep 28 08:59:40 2013, Hugmeir wrote:
I use -s a lot. -- Father Chrysostomos |
The RT System itself - Status changed from 'new' to 'open' |
From @rjbs* Brian Fraser <perlbug-followup@perl.org> [2013-09-28T11:59:40]
Not happening. -- |
From @HugmeirOn Sat, Sep 28, 2013 at 11:35 PM, Ricardo Signes
Boo. Oh well. I'll look into getting the segfault fixed; I'm ambivalent to the |
From @rjbs* Brian Fraser <fraserbn@gmail.com> [2013-09-28T23:05:18]
There exist programs written in 1994 and running continuously since then I think the number of such programs we'd break by deprecating/removing -s would -- |
From @TuxOn Sat, 28 Sep 2013 10:08:16 -0700, "Father Chrysostomos via RT"
I tend to replace -s procedures with documented Getopt::Long, but I -- |
From @LeontOn Sat, Sep 28, 2013 at 5:59 PM, Brian Fraser <perlbug-followup@perl.org>wrote:
I don't think that's a good idea either, but it may be reasonable to limit Leon |
Migrated from rt.perl.org#120039 (status was 'open')
Searchable as RT120039$
The text was updated successfully, but these errors were encountered: