Typos in code
-
I spotted one last week, it was something I had written about a year ago, and edited quite a few times since, and never noticed the typo. Can't remember what it was now, but the typo made a different, but real, word to the one I was aiming for.
Every man can tell how many goats or sheep he possesses, but not how many friends.
What was it?
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
Do you make them? I recently made some changes to a library I wrote and misspelled 'Source'. Soon after a co-worker came to me and asked what the 'Sauce' Property did... :-O That was right before the Oulook (missing a T) incident...
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}None that my compiler didn't catch.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
Do you make them? I recently made some changes to a library I wrote and misspelled 'Source'. Soon after a co-worker came to me and asked what the 'Sauce' Property did... :-O That was right before the Oulook (missing a T) incident...
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}We have one in one of our module name (Presnetation) which has propgated to our namespace. What is interesting is that will see the correct spelling almost next to the bad spelling.
-
We have one in one of our module name (Presnetation) which has propgated to our namespace. What is interesting is that will see the correct spelling almost next to the bad spelling.
Clifford Nelson wrote:
propgated
propagated perhaps?
Silence is golden... but duct tape is silver!! Booger Mobile - My bright green 1964 Ford Falcon - check out the blog here!! | If you feel generous - make a donation to Camp Quality!!
-
Do you make them? I recently made some changes to a library I wrote and misspelled 'Source'. Soon after a co-worker came to me and asked what the 'Sauce' Property did... :-O That was right before the Oulook (missing a T) incident...
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}Best one I remember is about 35 years old. Interdata assembler had instructions BAL (Branch and Link - subroutine call) and ABL (Add to Bottom of List - add an item to a dequeue structure). One of my cow-orkers had a subroutine that (a) didn't do its thing when called from one particular spot and (b) got progressively mutated. Much head-slapping (from him) and laughter (from the rest of us) followed. Cheers, Peter
Software rusts. Simon Stephenson, ca 1994.
-
Do you make them? I recently made some changes to a library I wrote and misspelled 'Source'. Soon after a co-worker came to me and asked what the 'Sauce' Property did... :-O That was right before the Oulook (missing a T) incident...
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}I recently refactored "seperator" into "separator" (though I was not the one to make the initial typo). And every now and then I come across a code comment that I messed up.
-
Do you make them? I recently made some changes to a library I wrote and misspelled 'Source'. Soon after a co-worker came to me and asked what the 'Sauce' Property did... :-O That was right before the Oulook (missing a T) incident...
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}Not a typo as such, but a while back I decided that come heck or high water I was going to spell "threshold" with two dadgum Hs the way it ever-lovin' sounds! This included not only variables and properties, but values in the database. A few years later I decided I really was being silly so I refactored them to the correct accepted spelling. Changing the values in the database was the hard part -- I had to add the new spelling, bounce the Services, and then I could delete the old values. :sigh: To quote one of my favourite song writers: "I was kicking my own a$$ upside down."
-
Clifford Nelson wrote:
propgated
propagated perhaps?
Silence is golden... but duct tape is silver!! Booger Mobile - My bright green 1964 Ford Falcon - check out the blog here!! | If you feel generous - make a donation to Camp Quality!!
its txtspeak, not typo. :)
Signature construction in progress. Sorry for the inconvenience.
-
Do you make them? I recently made some changes to a library I wrote and misspelled 'Source'. Soon after a co-worker came to me and asked what the 'Sauce' Property did... :-O That was right before the Oulook (missing a T) incident...
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}Ever since intellisense started to work as it should, all my spelling went down the drain. Luckily, the guys who brought me working intellisense also brought me "rename thins thing".
FILETIME to time_t
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy -
What was it?
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
Do you make them? I recently made some changes to a library I wrote and misspelled 'Source'. Soon after a co-worker came to me and asked what the 'Sauce' Property did... :-O That was right before the Oulook (missing a T) incident...
It's an OO world.
public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
} -
I recently refactored "seperator" into "separator" (though I was not the one to make the initial typo). And every now and then I come across a code comment that I messed up.
I recently ran across three different misspellings (one each in three different projects). It was the exact same word in the exact same comment in the exact same method that someone had copied from one project to another (twice). I was embarrassed enough to learn that I was the one who wrote the original (misspelled) comment (quite a few years ago) :-O . I really didn't need to know that I was also the one who copied it (twice) instead of adding it to our class library. (In addition, I apparently copied the code without reading the comment - which means it probably wasn't even worth writing in the first place). :sigh: --Tim Sygitowicz
