So, one guy from my uni posted this on his facebook,
He passed an int, without checking it and it was an int coming from an wrong computation. Compiler really didn't like it.
Had you ever got any "interesting-funny" compiler messages?
So, one guy from my uni posted this on his facebook,
He passed an int, without checking it and it was an int coming from an wrong computation. Compiler really didn't like it.
Had you ever got any "interesting-funny" compiler messages?
Code - functions and small libraries I use
It’s 2014 and I still use printf() for debugging.
"Programs must be written for people to read, and only incidentally for machines to execute. " —Harold Abelson
I haven't encountered any personally. But it would probably brighten my day if I saw one like that myself.
For sure, it would make me smile too.Originally Posted by Matticus
Code - functions and small libraries I use
It’s 2014 and I still use printf() for debugging.
"Programs must be written for people to read, and only incidentally for machines to execute. " —Harold Abelson
*That* isn't a compiler error message.So, one guy from my uni posted this on his facebook,
He passed an int, without checking it and it was an int coming from an wrong computation. Compiler really didn't like it.
Had you ever got any "interesting-funny" compiler messages?
Post made with -pedantic option at 0200 hours
Not everything that can be counted counts, and not everything that counts can be counted
- Albert Einstein.
No programming language is perfect. There is not even a single best language; there are only languages well suited or perhaps poorly suited for particular purposes.
- Herbert Mayer
I wish gcc had a sense of humor...
And I also wish g++ had smaller error messages but alas, I am probably just bad at C++ XD
Right. Rather, it's the message returned from the NSInvalidArgumentException object.
Code:#include <cmath> #include <complex> bool euler_flip(bool value) { return std::pow ( std::complex<float>(std::exp(1.0)), std::complex<float>(0, 1) * std::complex<float>(std::atan(1.0) *(1 << (value + 2))) ).real() < 0; }
I checked back his post and he says "message from Xcode debugger". Should we "accept" it?
Code - functions and small libraries I use
It’s 2014 and I still use printf() for debugging.
"Programs must be written for people to read, and only incidentally for machines to execute. " —Harold Abelson
