Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

Re^3: What operator should perl5porters use for safe dereferencing?

by ikegami (Pope)
on May 30, 2012 at 16:06 UTC ( #973329=note: print w/replies, xml ) Need Help??

in reply to Re^2: What operator should perl5porters use for safe dereferencing?
in thread What operator should perl5porters use for safe dereferencing?

That eliminates ~> as far as I'm concerned. Way too similar to ->.

Replies are listed 'Best First'.
Re^4: What operator should perl5porters use for safe dereferencing?
by Tanktalus (Canon) on May 30, 2012 at 16:34 UTC

    The main problem I have with ~> is the change in shift key. The ~ is on the left side of the keyboard (at least my US-style keyboard), so touch typists will use the right shift key. > is on the right, thus the use of the left shift key. tchrist's "Twister" moniker comes in to play here - try typing it out a few times to see how easy/difficult it is. Maybe for hunt-and-peck typists there won't be much difference. For touch typists, we could come up with an alternative that was less discordant (such as ->>).

    The fact that a quick glance at code wouldn't always tell the difference between -> and ~> is, in my opinion, both a positive and a negative. Positive in that they are so tightly related and often that's good enough, but negative in having to mentally switch gears to actually pay attention and notice it when it matters.

        I used to love typing on those :) I also really liked how the mouse was plugged into the keyboard in the PS/2 version, making it a much more comfortable experience than PCs at the time with not-long-enough mouse cables to reach the box on the ground.

      Hmm, maybe Iím using my keyboard wrong, but Iím one of those people who more often than not use the right shift (the left being tiny due to the European style 102-key key layout). Even if I had a preference for the left shift key though, the thing would be the same: press shift, press one of the keys, press the other key with the other hand, release shift. If anything, -> is ever so slightly harder to type because the precise timing needed between the two keystrokes, whereas ~>ís both characters are on the same shift level on English layouts at least.

      My problem with ~> is that on certain font sizes with certain fonts and certain hinting settings, FreeType makes the tilde look like a straight bar.

        Hmm, I learned touch typing, but I no longer venture past qwerty by touch, even now that I've lost my numpad -- kinda weird
      An excellent point. I hope it gets taken into consideration.

      - Boldra
      The ~ is on the left side of the keyboard (at least my US-style keyboard), so touch typists will use the right shift key...

      There are people who use the right shift key? Seriously?

      Huh. I use the right shift key about as often as the right alt and right ctrl keys -- which is to say, somebody could sabotage those keys as an April Fools joke so that pressing them does nothing, and it could be five years or more before I notice, depending on when I finally get around to cleaning out my keyboard thoroughly (as opposed to just quickly running an ISO long narrow object between the keys to get most of the hair out, which is what I usually do).

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://973329]
[marinersk]: sub newtest{my $expected_result = &target('foo'); my $actual_result = &target('foo'); if ($actual_result eq $expected_result) { &tdd_success(); } else { &tdd_fail(); } } # Test works after three years!
[choroba]: or nobody bothered...
[choroba]: The problem was bigger, as the test tried to call a method that didn't exist anymore
[marinersk]: :: ducking ::
[choroba]: because, someone renamed the method, but didn't notice it was used in the test, as the test was skipped
[marinersk]: Well, if the method doesn't exist, it would be hard to pass the test.
[choroba]: later, someone removed the new method, as all its usage places were safe, but didn't notice the test still used the old name
[choroba]: fortunately, it wasn't that hard to replace the method and fix a few remaining failures due to the changes we did to the codebase over the years
[marinersk]: choroba Sounds like a process improvement opportunity; tests may not all need to be run, but they should all be compiled with perl -c before check-in/promotion happens.
[choroba]: so, now I have the test, so I can start making changes in the code. Back to the original ticket, yay!

How do I use this? | Other CB clients
Other Users?
Others having an uproarious good time at the Monastery: (15)
As of 2017-05-25 15:12 GMT
Find Nodes?
    Voting Booth?