The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
This usually happens by accident when they implement the property before defining the accompanying field. It's happened to me a couple of times.
I compile at the highest warning level and VS2013 doesn't catch this error at compile time.A "self-referencing property" compile-time warning would be nice to have.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 - You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 - When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
I suspect that the code comes from a keyboard dyslexic like myself. Since he/she regularly mis-types lenght (see?) they though it would be a good idea to cater for it... unofrtuantely they misspselt it in the function too.
I recently started working with Python. The IDE I use highlights every potential typo and stylistic error as I type. A variable name like Lenght would be flagged immediately, even though it is syntactically legal.
My goal when coding with the IDE is zero flaggings of code. In the long run it is worth it.
Handed in my letter of resignation last week.
Just one more month to go and I'm off working for another company
Not sure which one yet, but I'll have plenty of new learning opportunities
I've been doing the same thing at my current company for far too long and just needed a new challenge.
Can't wait to get started on a new job
I didn't know you guys cared so much, but don't worry about me being out of a job.
I've got two possible employers lined up to take me on board and plenty of backup, even when things go awry