|
|
It's a pity that this scheme for line-numbering does not work
|
|
|
|
|
OMG!!!!!!!!!!!!!!!!!!! ripe my eyes out now!!!!!!
|
|
|
|
|
I think a part of me just died. I counted at least 8 things wrong with that snippet
|
|
|
|
|
Not bad there are 9 lines of actual code
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Ah, but only four of those are unique. That works out at 2 errors for each unique line of code
|
|
|
|
|
You missed a couple:
9) Undocumented
10) 100 numeric states. How do you keep track of which one does what...
No trees were harmed in the sending of this message; however, a significant number of electrons were slightly inconvenienced.
This message is made of fully recyclable Zeros and Ones
|
|
|
|
|
Other than the missing semi-colon on the first statement, that's how it should be.
|
|
|
|
|
Well I have very good idea what happened. The programmer tried to implement fall-through switch, which is not allowed in C#. When he discovered that, he decided to work around it with those goto calls.
He was either rusty on his goto or he could not figure how to "declare" a label or maybe the language he was using before did allow something similar... That's what happens when you switch languages. For a while you keep thinking in terms of the old language thus producing such jems.
|
|
|
|
|
He shoulda written it recursively 
|
|
|
|
|
He should have used the for- case pattern 
|
|
|
|
|
Could easily be c++ -> C# .
But still, this isn't nice in C++ as well.
You have the thought that modern physics just relay on assumptions, that somehow depends on a smile of a cat, which isn’t there.( Albert Einstein)
|
|
|
|
|
OriginalGriff wrote: Fortran programmer.
Hehe, he is still alive!
|
|
|
|
|
state=1<br />
for (int n = state; n<101;n++)<br />
{<br />
switch (n)<br />
{<br />
case 1:<br />
<br />
case 2:<br />
<br />
<br />
case 3: <br />
<br />
............<br />
<br />
<br />
case 100:<br />
<br />
<br />
}<br />
}
What could be easier than that 
|
|
|
|
|
If the syntax is correctet, the compiler doesn't complain...
thank you for teaching me that -
int state=1;
switch (state)
{
case 1:
goto case 2;
case 2:
goto case 3;
case 3:
goto case 4;
case 4:
break;
}
|
|
|
|
|
I'm still in favor of
which compiles just fine.
Luc Pattyn [Forum Guidelines] [My Articles]
The quality and detail of your question reflects on the effectiveness of the help you are likely to get.
Show formatted code inside PRE tags, and give clear symptoms when describing a problem.
|
|
|
|
|
Whatever he was trying to do, It results in what Luc has written.
Ultimately, he ended up getting the same result with extra lines of code.
|
|
|
|
|
looooool - OMFG, took me a few minutes before I could type again after reading this - ROFL!!!
GSoC 2009 student for SMW!
---
My little forums: http://code.bn2vs.com
---
70 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69 66 65!
|
|
|
|
|
Shite!
Sometimes while reading the programming forums, I just feel like jabbing a fork into my eyes.
It is a crappy thing, but it's life -^ Carlo Pallini
|
|
|
|
|
I guess the programmer of the snippet below found a function to fill a DropDownList and adjusted it just enough to fill a TextBox...
Private Sub ShowName(ByVal id As String)
Dim daNames As New SqlDataAdapter("SELECT ID, NAME FROM TBL_NAMES", ConnectionString)
Dim dsNames As New DataSet("NAMES")
daNames.Fill(dsNames, "NAMES")
Dim drNames As DataRow = dsNames.Tables(0).NewRow
drNames("ID") = -1
drNames("NAME") = ""
dsNames.Tables(0).Rows.InsertAt(drNames, 0)
If dsNames.Tables("NAMES").Rows.Count > 0 Then
Try
Dim drs() As DataRow = dsNames.Tables(0).Select("ID = " & id)
txtName.Text = drs(0).Item("NAME").ToString
Catch e As Exception
'
End Try
Else
txtName.Text = ""
End If
End Sub
|
|
|
|
|
DataAdapter and DataSet are so powerful they can be used to do anything... poorly.
|
|
|
|
|
Cool! Can i quote that?
I had a boss who used those as his all powerful silver bullet, and many a wtf ensued.
-------------------------------
Carrier Bags - 21st Century Tumbleweed.
|
|
|
|
|
|
#if (LIBRARYFLAG)
using Product.Client;
#else
using Product.Server;
#endif
using Product.Server;
To explain - we have the same services defined in Client and Server - this is using WCF. For development we set off LibraryFlag so use the services directly - without using WCF (it is faster and makes debugging easier)
Of course, if you create a new service, then dont create the client service, and set LIBRARYFLAG, resharper pops up a "Press alt-enter to add the 'using'" message.
I musta pressed it - so now it adds the using for the Server version.
Ohh it took me a while to spot what was happening!
___________________________________________
.\\axxx
(That's an 'M')
|
|
|
|
|
There are more #if #endif -related ReSharper bugs. Here is one of them which I spotted some time ago:
I you'd enable generating XML documentation in your project settings, you will get warnings in every place where you didn't make documentation. So far so good. However, once upon a time I wanted to have a different description for debugging and realase builds.
#if DEBUG
#else
#endif
public class Damage : Occurance
C# compiler wasn't complaing, but ReSharper wanted me to add another summary.
Greetings - Jacek Gajek
|
|
|
|