-
Notifications
You must be signed in to change notification settings - Fork 540
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
prototype() with no arguments #14376
Comments
From @cpansproutprototype() is not documented as accepting no arguments. But it does accept no arguments, and corrupts the stack in the process: $ ./perl -Ilib -le '$,=" "; print 1,2,3,prototype(),4,5,6' Here, it steals 3 from the stack and replaces it with undef. Here is a more intriguing example: $ ./perl -Ilib -le 'print "CORE::undef", prototype()' Should prototype() be illegal? Or should it mean prototype($_)? -- Father Chrysostomos |
From @rgsOn 28 December 2014 at 23:17, Father Chrysostomos
Well, according to itself, it requires one argument: perl -E 'say prototype"CORE::prototype"' which is probably an implementation detail. I see no strong objection against |
The RT System itself - Status changed from 'new' to 'open' |
From j.imrie1@virginmedia.comOn 28/12/2014 22:17, Father Chrysostomos (via RT) wrote:
I'd go for the latter, prototype($_), in line with oct(), say(), print() |
From @cpansproutFixed in eb4ec35 to infer $_. -- Father Chrysostomos |
@cpansprout - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#123514 (status was 'resolved')
Searchable as RT123514$
The text was updated successfully, but these errors were encountered: