NotImplementedException not implemented
-
Be fair: we've all had days like that. Granted, one usually fixes it the next day...
"There are three kinds of lies: lies, damned lies and statistics." - Benjamin Disraeli
Yeah - it's probably existential despair at what the code has to do - it is a filter function run on the client side that would be much more healthy if implemented as an SQL WHERE clause.
-
Was wondering why one of my unit tests was passing even when nonsense values were passed in...found:-
if (row != null)
{
if (!row.IsNull(fieldName))
{
double fieldValue = (double)row[fieldName];
// ok.. now what...
}}
What indeed....
Like one of my classmates from Purdue who wrote a NotImplementedExceptionEx which threw itself in the constructor. He never figured out why trying to throw one caused his program to abruptly exit.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
-
Like one of my classmates from Purdue who wrote a NotImplementedExceptionEx which threw itself in the constructor. He never figured out why trying to throw one caused his program to abruptly exit.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
Did he find help on StackOverflow? :D
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Did he find help on StackOverflow? :D
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
More importantly: did he ever give help on StackOverflow?
Software Zen:
delete this; -
More importantly: did he ever give help on StackOverflow?
Software Zen:
delete this;Nah...he couldn't earn enough points to answer a question!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
Like one of my classmates from Purdue who wrote a NotImplementedExceptionEx which threw itself in the constructor. He never figured out why trying to throw one caused his program to abruptly exit.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
I'm guessing he was a dual major - CS / Philosophy - and was attempting to express existentialist nihilism through code.
-
I'm guessing he was a dual major - CS / Philosophy - and was attempting to express existentialist nihilism through code.
AFAIK, he ended up switching to the hardware aspect of computing and has done much better.
What do you get when you cross a joke with a rhetorical question? The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism. Do questions with multiple question marks annoy you???
-
Be fair: we've all had days like that. Granted, one usually fixes it the next day...
"There are three kinds of lies: lies, damned lies and statistics." - Benjamin Disraeli
Not always. I've had the following in one of mine for years:
else
{
/* I don't know what to put here */
} -
Did he find help on StackOverflow? :D
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
More importantly: did he ever give help on StackOverflow?
Software Zen:
delete this; -
Was wondering why one of my unit tests was passing even when nonsense values were passed in...found:-
if (row != null)
{
if (!row.IsNull(fieldName))
{
double fieldValue = (double)row[fieldName];
// ok.. now what...
}}
What indeed....
You clearly need to write some unit tests for your unit test :)
