in reply to Re: Thoughts on replacing -> with .in thread Thoughts on replacing -> with .
Note that =~ and ~= are both valid Perl already.
Hmm, I don’t see ~= in perlop; and ~ is the unary bitwise negation operator, so it wouldn’t make much sense to have ~=. What is it?
It is like += and .=, which modify the left-hand side by the right hand side.
$a += $b adds the right hand side ($b) to the left hand side, $a, and assigns the result to $a.
$a .= $b appends $b to $a and assigns the result to $a.
$a ~= $b xor's $b and $a and assigns the result to $a.
As this is a relatively uncommon use, it maybe makes this interchange currently even harder to spot than later the use of =~ and ~=.
But XOR-assign is supposed to be $a ^= $b...
$a ~= $b
None - I don't code
0 - Ticker-tape is a purer representation of a Turing Machine
1 - A laptop screen or single monitor desktop workstation
1 - And it's cracked. And I like practicing my trade while lying on a bed of nails
2 - The standard dev kit suits me fine
3 - Fewer than three monitors wouldn't present enough insight into what I'm working on
4 - Everyone else has two or three. I'm not like everyone else
5 - This configuration reminds me of the 1987 5-cylinder VW Passat my parents let me drive in high school
6 - I saw such a thing on the Internet, and had to have it
6 - Because I haven't figured out how to add more
7 - I need all the luck I can get, for this code to work
8 - Because my power strip had eight outlets available
9 - A 3x3 array was the the most I could fit into my Faraday shielded SHTF headquarters
More than 9 - Most of them are just displaying graphs / mock code to make the boss think I'm doing something critical
Results (562 votes). Check out past polls.