M
Mac
myself and at least one other person. That defines a clear
majority.
I agree.
And in a pinch, the "other person" could be hypothetical. ;-)
Mac
myself and at least one other person. That defines a clear
majority.
<snip>Dear c.l.c regulars,
How about codifying a list of acceptable acronyms on c.l.c?
Comments are welcome.
I like LART, in particular...
I'm sure I have enountered it before in the jargon file, but not in the
wild (as far as I remember).
In said:<snip>
Y2K
Is this year 2000 or year 2048 ?
I can't believe I've read all of the posts so far and noone has commented
the lack of "K&R" and "K&R2"
Why should anyone codify acceptable acronyms. Document those that are in
common use today (eg in a FAQ) and that noone complains about.
Huh? Its meaning is perfectly clear as far as I know,
modulo the R's standing for either "repair" or "recall."
Not that it's ever been used in this group AFAIK...
Because people who write that most often use "wtf?" (lowercase),
and aren't worth reading anyway. It's a statement of
lack-of-knowledge and obscenity in one. I've never read
"WTH" before, and I'm not entirely sure it means what you
imply it means (but can't come up with anything better, and
looks like Acronym Finder agrees with you) except in longer
phrases such as "WTHDYTYA (TTMT___)?". ;-)
And maybe even WLOG ("without loss of generality"), which might
pop up from time to time here or in related groups.
You skipped the obvious: UB.
And its less obvious and cutesier siblings IDB and USB.
Tak-Shing Chan said:Dear c.l.c regulars,
How about codifying a list of acceptable acronyms on c.l.c?
Slartibartfast said:In a similar vein to RTFM is STFW. Surprised I haven't seen it here before.
Well, there's always the ever-popular STFU What the heck is STFW
anyway?
Search The Friendly Web.
A Google search for "fubar" would broaden your horizon.
Which is why I said it's not needed.
Years aren't memory bits/bytes/words, so there is no place for ambiguity.
In <[email protected]>
Because it's NOT obvious: both undefined behaviour and unspecified
behaviour are equal candidates for this abbreviation, therefore neither is
the obvious meaning of the expression.
A Google search for "fubar" would broaden your horizon.
Can't remember ever seeing it. If we start throwing in everything we
think it might be useful, the list will become unmanageably large
(and, therefore, useless) instantly.
We did very well without them until now, thank you. Especially
considering that USB already has a very well defined meaning in
computing.
Is that really what it means, or is it a skillful situational
improvisation? In either case, thanks...
[snips]
I like LART, in particular...
I'm sure I have enountered it before in the jargon file, but not in the
wild (as far as I remember).
You can't have been around too long, then; the LART and its companion tool
the cluebat have been used fairly frequently around usenet.
In said:groups.google.com shows 349 occurrences of "fubar" in comp.lang.c. A
number of them are within e-mail addresses; mahy of the others are in
discussions of the origin of "foo".
In said:[snips]
Years aren't memory bits/bytes/words, so there is no place for ambiguity.
Yet hard drive capacity - measured in bytes - typically uses powers of 10,
not of 2: 1Mb is 1,000,000 bytes, not 1,048,576.
Apparently, the bits/bytes/words distinction isn't sufficient.
In said:I don't think I've ever seen "UB" used in this newsgroup to refer to
"unspecified behavior". As far as I know, it has always meant
"undefined behavior" (probably because we talk about undefined
behavior a lot more often than we talk about unspecified behavior.)
Until Dan raised the point, it never occurred to me that UB might mean
"unspecified behavior". A cursory look in groups.google.com tends to
confirm this, but of course I haven't looked at all 2670 occurrences
Dan, can you provide a counterexample?
How so? I see only the commonly accepted definition on the first
page of Google results (and in the underlined definition link).
I assume you're not referring to either the VAX instruction or the
Do you *really* think that such a list of acronyms, even if it
ever gets "codified" by Paul or some other guy, is going to affect
the established Usenet subculture in any way?
It's not like people
are going to stop using "ISTR" in sentences just because some guy
with a website thinks it's not self-explanatory.
One that is not applicable in c.l.c, yes.
And I *have* seen
IDB used (in context, of course) in this newsgroup in the past.
It's very rare, and appropriately so.