- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
yeah, ok it's full of negatives but it's pretty obvious what it means. If it took you a while to figure it out maybe it's a good job that (or no wonder that) you are an ex-tutor. Sure I'd also explain to him that it could be clearer and maybe dock him a few points off of his assignment but it's not that bad.....
Admin
In C++, it's actually not recommended to add an "operator bool() const" to a class that has valid/invalid semantics, but only a "bool operator !() const" to avoid unwanted implicit conversions. To query an object o for validity, a user then has to write "!!o" where the second application of ! is of course the built-in boolean negation, but the first one is the custom operator ! of the class. The advantage over a method like let's say "bool valid() const" is that this works with any type to which the operator ! can be applied, such as bool itself, which may be important in template code.
( And then they said that Haskell was confusing. :-) )
Admin
And more symbols is more perl is more the hack is more better !
Admin
"Having just inherited a mammoth, ..."
Please don't start sentences this way, I almost had a heart attack.
Admin
I think the answer should be obvious.
The file why.txt was generated by the previous programmer just before he lost his last tenuous grip on sanity.
Which reminds me. If you ever see a man carrying a fire axe, walk the other way. Quickly.