Representative compile error
-
In the midst of a large C++ codebase (different code, same vendor as the previous WTFs):
[code]
somedir/SomeSourceFile.C:508: error: ‘assert’ was not declared in this scope
[/code]Seriously. How do you forget to [s]
#include <cstdlib>
[/s]#include <cassert>
? Morons...
-
I think that
std
is a horrible abbrevation for standard.
-
Fortunately it no longer has the alternative definition because the hip trendy equivalent is now STI.
-
Seriously. How do you forget to #include <cstdlib>? Morons...
assert
is in<cassert>
, not<cstdlib>
...Which is a particularly ironic mistake given that if
<cstdlib>
gives youassert
it is only being included transitively and will probably break in the future considering that's actually not standard-compliant -- which is how I'd guess you'd wind up with your original situation in the first place. (They included<header1>
which transitively includedassert
in their compiler, but not under yours.)
-
I think that std is a horrible abbrevation for standard.
I always see these trucks because their witless use of the Jesus Fish flags them in my Atheist Sensors, then I chuckle at "STI". Perhaps needless to say, I was delighted to find that their web site is a WTF unto itself. I was also amused to learn how many different things STI stands for (http://en.wikipedia.org/wiki/STI).
-
We have a plumbing supply company around here named POS, I see the trucks around all the time.
-
assert is in <cassert>, not <cstdlib>...
Which is a particularly ironic mistake given that if <cstdlib> gives you assert it is only being included transitively and will probably break in the future considering that's actually not standard-compliant -- which is how I'd guess you'd wind up with your original situation in the first place. (They included <header1> which transitively included assert in their compiler, but not under yours.)
Thanks for the correction. I was recalling it being in stdlib.h, but that's from a slightly odd C implementation (Newlib). So, assert.h it is!
Either way... it just gets worse from here:
[code]
someotherdir/SomeOtherSourceFile.C:385: error: ‘strlen’ was not declared in this scope
[/code]
And that's just one of many...
-
I think that
std
is a horrible abbrevation for standard.Yeah. Ever wondered if there's a
std::sign()
function and if so, what header it's in? Googling forstd::sign
is hilarious. Preferably do this at work, and have somebody watch the search results over your shoulder.Filed under: There isn't.
-
The codebase used a different compiler or
Clib before this!?
-
Yeah. Ever wondered if there's a std::sign() function and if so, what header it's in? Googling for std::sign is hilarious. Preferably do this at work, and have somebody watch the search results over your shoulder.
I've had a few mildly amusing searches when working on LaTeX stuff1; I had one search one time that returned some rather NSFW stuff, but I forget what it was.1I feel like a tool actually writing it with the mixed case like that, but I felt like I needed to for people to know what I was talking about.
-
I feel like a tool actually writing it with the mixed case like that, but I felt like I needed to for people to know what I was talking about.
In case we thought you were dressed in latex instead? And why didn't you take the trouble of putting the A in a smaller font above the L, and then TEX, but with a bigger E, and in computer modern, of course?
-
You mean like LATEX? Or some crazy zalgofont?
(Like I'd know how LaTeX is supposed to be written)
-
Top left:
-
Seriously? The fuck is up with that?
-
"Donald Knuth instructs that it be typeset with the "E" below the baseline and reduced spacing between the letters. This is done, as Knuth mentions in his TeXbook, to distinguish TeX from other system names such as TEX, the Text EXecutive processor (developed by Honeywell Information Systems)."
Because choosing a unique name would have been too much work.
Basically, it was Knuth being kind of a dick, and Leslie Lamport (author of Latex) just following suit.
-
Seriously? The fuck is up with that?
It's weird, because usually open source projects are so good at visual design and branding.
-
What's up with the pronunciation? Why do they pronounce the X as /k/ instead of /ks/ like it's normally pronounced in English and most other languages that have X in their alphabets?
-
It's weird, because usually open source projects are so good at visual design and branding.
Here's the thing though... Tex is weird on that line because it is pretty well-respected for its typographical layout and aesthetics.
What's up with the pronunciation?
Because it's not spelled 'tee, eee, ex'; it's spelled 'tau, epsilon, chi'. (The root of "technical", actually.) :eyeroll:
-
it's spelled 'tau, epsilon, chi'.
What? I don't even...
Even if you accept that WTF mixing of characters from different alphabets in a single word, the pronunciation still isn't right. In modern Greek, it's pronounced more or less exactly like ch in German — either /ç/ (German ich) or /x/ (German ach), depending on what follows it. The closest χ has ever come to being pronounced /k/ is in ancient (~500BC) Greek, where it is believed to have been pronounced /kʰ/ or /ks/, depending on the dialect (the latter of which is how X got into Latin, and thus languages that use the Latin alphabet, with a /ks/ pronunciation, which also brings us right back to the original point).
Knuth being kind of a dick
Did he come up with the pronunciation, too? He should stick to computers, because naming stuff is hard.Filed under: Pendantic, but sufficiently dickweedy?
-
Even if you accept that WTF mixing of characters from different alphabets in a single word
What? ...it's all Greek. And yes, ancient Greek is the inspiration. Here's what Wikipedia says:"The name TeX is intended by its developer to be /ˈtɛx/, with the final consonant of loch or Bach. The letters of the name are meant to represent the capital Greek letters tau, epsilon, and chi, as TeX is an abbreviation of τέχνη (ΤΕΧΝΗ – technē), Greek for both "art" and "craft", which is also the root word of technical. English speakers often pronounce it /ˈtɛk/, like the first syllable of technical."
Like I said, I still feel like a tool capitalizing it the way Knuth suggests, but it is at least consistent on that front. (At least, as far as I can tell; I'm not a linguist.)
-
-
At least the L of LaTeX isn't. That would be Λ in Greek.
Sure, but "TeX" was set long before Latex came around. So it was either drop the name connection to the base system, find some pun on an ancient Greek name, or go with the mixed-alphabet name.It's a little like C++, where the name doesn't exactly make sense if you think too hard about it.
-
-
LᴬTᴇX?
-
Almost there, Ben, but the E should be at normal height, and just below the baseline. Keep trying!
-
What? I don't even...
The closest χ has ever come to being pronounced /k/ ...
I don't know how you pronounce TEX, but it [i]is[/i] pronounced "tech" /tex/ as in German, not "tek".
-
-
Beware, blakeyrat. You may have a name, but that doesn't mean you won't get killed before the end of the episode.
-
My favorite line: "Quick! Let's get out of here before one of those things kills Guy!"
-
My favorite line is: "I KNEW IT" when they tell him it's all true. Comedy genius.
-
"tech" /tex/ as in German,
You mean "kh" as in
http://cdn3.nerdapproved.com/wp-content/uploads/2011/07/khaaaaan.jpg?874fb4
-
In lojban, it's pronounced
laTEK
(the all-caps second syllable is important because the second-last syllable is stressed otherwise)
-
The whole scene with the transporte-- er, 'digital conveyor', was awesome too. "You'll need to build a weapon. Look around, can you form some kind of... rudimentary lathe?" "GET OFF THE LINE, GUY!"
... actually all of Guy's lines are the best. "What are you grinning about?" "I'm just so jazzed to be on the show!"
"Why are you opening the door? We're on an alien planet! IS THERE AIR? YOU DON'T KNOW!!!"
-
-
You Sir, need to get a life.
He has one. Unfortunately, it's still in his mother's basement.
-
When it's not in dwarven fortresses.
-
You Sir, need to get a life.
I let this slide the first time, but every time I read it, it bothers me more:
You, sir, need to get a life.
- The name or honorific of the person you are addressing should be set off with commas both before and after.
- Unless Her Majesty has bestowed a title on @ben_lubar, which I'm pretty confident she has not, he's just a common
gentleman, and "sir" should not be capitalized.
-
Unless Her Majesty has bestowed a title on @ben_lubar, which I'm pretty confident she has not, he's just a common gentleman, and "sir" should not be capitalized.
Ben's an American, fuck your old world shit.
Signed, Sir Blakey of Rat, Esquire, Archduke of Nationalist Trolling.
-
Ben's an American
That's one of the (many) reasons I'm confident Her Majesty hasn't bestowed a title on him.
-
Good because if he had we'd have to throw him off a ship into Boston Harbor.
Sorry, them's the rules.
-
Can we do it anyway? Please?
-
Good because if he had we'd have to throw him off a ship into Boston Harbor.
Judging from the "WTF happened to Windows 9" thread, he'd probably get a better internet connection there...
-
Ben's an American, fuck your old world shit.
Signed, Sir Blakey of Rat, Esquire, Archduke of Nationalist Trolling.
Sir, I write with great passion and indignance at your attitude! I do bite my thumb at thee!
-
Unless Her Majesty has bestowed a title on @ben_lubar, which I'm pretty confident she has not, he's just a common gentleman, and "sir" should not be capitalized.
Someone who publicly admits to playing DF and knowing Lojban should be addressed as sirrah, probably, anyway.
-
Someone who publicly admits to playing DF and knowing Lojban should be addressed as "Hey, dumbass!"
FTFY
-
Not even commiserating the lack of fun they're 'enjoying'?
-
- The name or honorific of the person you are addressing should be set off with commas both before and after.
- Unless Her Majesty has bestowed a title on @ben_lubar, which I'm pretty confident she has not, he's just a common <s>gentle</s>man, and "sir" should not be capitalized.
- Unless it's at the end of the sentence, as in: A good day to you, sir.
- The phrase "which ... not" should be put between dashes. The comma signals a subordinate clause, while this phrase is an interjection.
- Ben is just a common man? Sound the trumpets!
Just
pulling your legusing pedantic dickweedery, old chap.
-
Sir, I write with great passion and indignance at your attitude! I do bite my thumb at thee!
Fun fact, i enjoy collecting useless titles in video games and role playing games. If they had any validity and i listed all of them in the correct format for a name, my name would now be about 16 megabytes.
fortunately for everyone they have no validity outside of the game they were acquired it, but i still enjoy collecting them!
-
-
quite similar to that, yes!
except much much longer.
my favorite title i had was:
Lady Accalia, Mistress of the Fallen Oaks and the Lands, Waters, and Effects Thereof.
it sounds cool until one realizes that in the particular game we were playing at the time that title was the equivalent of my postal address.
:-D