Re: Spoken Code

The most common shortcut I take when speaking out perl code is leaving off the colon-colon separator in namespaces. Like, just saying "apache DBI" instead of "apache colon colon DBI". If there's potential ambiguity, I'll sound out one colon, but never both. Occasionally one of the pedants I work with will "correct" this, but I don't care... to me it is correct.

One that actually annoys me is when the more micro$ofty types call a backslash a "whack". Just erks me.

------------
:Wq
Not an editor command: Wq
[download]

Comment on Re: Spoken Code Download Code

Replies are listed 'Best First'.
Re: Re: Spoken Code by biosysadmin (Deacon) on May 21, 2004 at 16:22 UTC
I use the verbal shortcuts as well when telling people things to type on the command line: "cat \| grep dash n" instead of "cat \| grep space hypen n." I also have a (bad?) habit of thinking of \| and > as "into," as in "cat myFile \| grep foo \| wc -l" or "echo 'I Rock! > myFile." In both cases I think "into," and the character that comes out of my fingers is context-dependent (going into a file, or going into another program). I've never heard of the "whack" before. That's an interesting one.	[reply]
Re:^2 Spoken Code by Nkuvu (Priest) on May 21, 2004 at 17:12 UTC
Whack? microsoft-y? Weird. I first heard of whack from other students (way back in the day that I was in college). They were far from being microsoft-y.	[reply]
Re: Re: Spoken Code by sfink (Deacon) on May 23, 2004 at 02:23 UTC
I am neither micro nor soft, thank you very much, but \ to me is "backwhack". Which is odd, because I never use plain "whack" for anything. "forward whack", rarely, if the / is in close proximity to backwhacks. Normally just "slash" or "forward slash", though. And I've called * "splat" ever since someone described to me how it looks like a bug hitting a windshield at high velocity. Perl6 will reward this tendency, I believe.	[reply]


laziness, impatience, and hubris
	PerlMonks