if something isn't really pronouncable I usually "expand it".

While I understand your point, there's a long history of pronouncing abbreviations as they look rather than as their expansions. It's the problem of trying to communicate an exact sequence of letters that isn't a real word.

Say someone comes to me and asks, "this class has a method that returns the error but I can't remember what it is called, what is it?" If I answer "error string" he's likely to try using error_string(); I haven't been very helpful if the function is actually called errstr(). Sure, I might answer "EE-AR-AR-ESS-TEE-AR", but spelling things out makes for tedious communication (and is prone to its own sort of errors.)

Many abbreviations already have some sort of generally accepted pronunciation. Of course, scores of variations exist too; jargon isn't immune to dialect.

So, yes, /usr is usually slash-user, but do you call /etc slash-etcetera? You probably call it slash-et-see like everyone else. And tmp is "temp", not "temporary", right? Do you call var "various" or "var"? Is it "opt" or "optional"? How about "dev" or "devices"? While you probably pronounce "mnt" as "mount", I'd bet that you don't call /proc slash-process or /lib slash-library. And so on.

The same goes for common functions. The str in many standard C function names is, in my experience, generally pronounced "stir" and err as in errno or stderr is often pronounced as "air".¹

Here are some other examples of abbreviations that are often pronounced in their short forms rather than expanded. Of couse, I'm not claiming this list is definitive or authoritative in any way; these are just some examples from my experience:

• csh — seesh (rather than C-shell)
• ksh — koosh, oo like book (rather than korn shell)
• getc — get-sea (not get character)
• malloc — mal-luck (not memory allocate)²
• enum — ee-num (not enumeration)
• int — int (not integer)
• chmod — chuh-mod (not change mode)
• dir — dir (not directory)
• env — env or onv (not environment)
• sync — sink (not synchronize)
• umount — you-mount (not un-mount)
• ord — ord (not ordinal)
• lc — ell-see (not lowercase)
• eof — ee-oh-eff (not end-of-file)

and so on. . .

But, like the saying goes, "I say toe-may-toe; you say toe-mah-toe." It doesn't really matter as long as the right meaning is communicated.

1. I've heard stderr pronounced as "standard error", "standard air", and, infrequently, "stud air". I fall into the second category.
2. Is it just coincidence that the use of malloc() often results in "mal" (or bad) luck? You decide... :-)

-sauoq
"My two cents aren't worth a dime.";

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.