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
Bug in perlop man page (=~ return value) #1283
Comments
From kompas@ceti.plI have answered on pl.comp.lang.perl with one of my favorite one-liners then friend of mine pointed to me, that perlop lies about =~'s return Binary "=~" binds a scalar expression to a pattern match. Which is true only in scalar context - in list context it returns the same I hope someone will fix perlop manpage in next revision (althought it is Greetings -- |
From [Unknown Contact. See original ticket]On Tue, 7 Mar 2000, Piotr Piatkowski wrote:
just because you don't understand perlop (or someone),
Remember there is more that one way to indicate success,
the section on =~ is just part of what you should read if you m/PATTERN/cgimosx /PATTERN/cgimosx If the `/g' option is not used, `m//' in list con- Examples: if (($F1, $F2, $Etc) = ($foo =~ /^(\S+)\s+(\S+)\s*(.*)/)) This last example splits $foo into the first two |
From @tamiasOn Tue, Mar 07, 2000 at 09:42:58PM -0800, David Dyck wrote:
Just because perlop is lying doesn't mean someone misunderstands it. ;)
Regardless, the original poster is correct. The documentation =~ should
The documentation for =~ should direct the reader to that section. Ronald |
From [Unknown Contact. See original ticket]On Wed, 8 Mar 2000, Ronald J Kimball wrote:
Yes, that's exactly what I meant. I was using bind operator in list But nevertheless, perlop manpage is a little misleading here, and IMHO it BTW, forgive me my English, it's not my primary language so I'm writing -- |
From [Unknown Contact. See original ticket]Looks like no-one else is gonna do it... *** perlop.pod.orig Wed Mar 8 09:22:04 2000 |
From [Unknown Contact. See original ticket]On Wed, 8 Mar 2000, Piotr Piatkowski wrote:
The please forgive my initial reply too, as I did not realize that Did you find the patch that Martyn Pearce <martyn@inpharmatica.co.uk>
I liked your yaph signature I kept on looking for the semicolons as I didn't dd:dcd$ perl -MO=Deparse,-q -le 's**02).4&9%4^[./4(%2^0%2,^([#+%2&**y%& -;^[%> s[]<02).4&9%4^[./4(%2^0%2,^([#+%2&> * tr/ -;[^/`-e"g-{a / % s//$_;/ee; One could stick a virus in there easily :-) |
From [Unknown Contact. See original ticket]On Wed, 8 Mar 2000, David Dyck wrote:
Yes, thank you.
Yeah, I was trying to make sig which, when run, would append to ~/.sig or -- |
Migrated from rt.perl.org#2280 (status was 'resolved')
Searchable as RT2280$
The text was updated successfully, but these errors were encountered: