|
If that's C#, it won't compile; you'll get a "Control cannot leave the body of a finally clause" compiler error.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Yes, you are right. So let's remove the last "return" (but not the File.ReadAllText).
|
|
|
|
|
That would compile on java, I think.
|
|
|
|
|
Really?
Which value would expect to be returned here?
try
{
return 1;
}
catch
{
return 2;
}
finally
{
return 42;
}
I think the C# compiler is doing the right thing. Either the return in the finally block is ignored, in which case it shouldn't be allowed, or it replaces any value returned from the try or catch blocks, which is just confusing.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Oh I wasn't saying it should be allowed, but I think it is.
|
|
|
|
|
FTSOTR, that does compile in Java (with a little syntactic fix) and returns 42.
|
|
|
|
|
You would be more likely to get that right if you added commentary:
try
{
return 1; // Genesis
}
catch
{
return 22; // Joseph Heller
]
finally
{
return 42; // Douglas Adams
}
|
|
|
|
|
|
Oh yes you can do so. But there is a catch - it's "catch 22".
Why did it take me so long to see it?
|
|
|
|
|
Your'e doing it wrong!
(Even catch blocks end in curly braces.)
Ciao,
luker
|
|
|
|
|
Richard Deeming wrote: If that's C#, it won't compile; you'll get a "Control cannot leave the body of a finally clause" compiler error. I had to play around. You can throw an error in the try/catch/finally segments and it will compile. Since I didn't enclose the routine in a try catch, the finally segment did blow up with an unhandled exception. Then I did put it in that logic:
try
{
int junk = trycat();
}
catch (Exception ex)
{
Console.WriteLine("caught exception {0}", ex.Message);
Console.ReadKey();
}
...
static int trycat()
{
try
{
throw (new Exception("Throwing an exception in try block"));
}
catch
{
throw (new Exception("Throwing an exception in catch block"));
}
finally
{
throw (new Exception("Throwing an exception in finally block"));
}
return 1;
}
|
|
|
|
|
Sigh.
public string ReadFile(string filename)
{
string contents = null;
try
{
contents = File.ReadAllText(filename);
}
catch
{
contents = File.ReadAllText(filename);
}
finally
{
contents = File.ReadAllText(filename);
}
return contents;
} Okay. Everybody happy now?
Software Zen: delete this;
|
|
|
|
|
Quitter - use recursion!
public string ReadFile(string filename)
{
try
{
return File.ReadAllText(filename);
}
catch
{
return ReadFile(filename);
}
}
Life is like a s**t sandwich; the more bread you have, the less s**t you eat.
|
|
|
|
|
brisingr@gryphon-pc$ cpmsg --process --msg "4433493" --forum "The Weird and The Wonderful" --code "Process"
ERROR: StackOverflowException was encountered.
brisingr@gryphon-pc$|
Bob Dole The internet is a great way to get on the net.
2.0.82.7292 SP6a
|
|
|
|
|
Maybe we need a more flippant programming language, for those of us who think like this:
try
{
// something
}
ifatfirstyoudontsucceed
{
// try again
}
thirdtimelucky
{
// and again
}
giveup // synonym for catch
{
// error handling
}
finally
{
// tidying up
}
|
|
|
|
|
Bernhard Hiller wrote: three is the magic number
It sure is!
Monty Python :
First shalt thou take out the Holy Pin.
Then, shalt thou count to three, no more, no less.
Three shalt be the number thou shalt count, and the number of the counting shall be three.
Four shalt thou not count, nor either count thou two, excepting that thou then proceed to three.
Five is right out.
Once the number three, being the third number, be reached, then lobbest thou thy Holy Hand Grenade of Antioch towards thy foe, who, being naughty in my sight, shall snuff it."
Alcohol. The cause of, and the solution to, all of life's problems - Homer Simpson
|
|
|
|
|
|
I like it. Another opportunity to bill the client.
|
|
|
|
|
|
When I was programming that, I thought: "It's in a catch block, then it can't throw an error!"
ProgramFOX
|
|
|
|
|
Mmmm... you seem determined to read that file, is it important?
|
|
|
|
|
No. The reading of the file isn't important.
That's a code from 2 years ago.
Now, I know how I can read files!
ProgramFOX
|
|
|
|
|
Timed out first time, then worked the second time?
|
|
|
|
|
ALTER PROCEDURE [dbo].[arUpdate]
@intForecastID int,
@strForecastName varchar(18),
@strBillTo varchar(12),
@strPOCName varchar(50),
@strPOCEmail varchar(100),
@strModifiedBy varchar(20),
@strComment varchar(3000),
@strDelMaterials varchar(8000),
@strData1 varchar(8000),
@strData2 varchar(8000),
@strData3 varchar(8000),
@strData4 varchar(8000),
@strData5 varchar(8000),
@strData6 varchar(8000),
@strData7 varchar(8000),
@strData8 varchar(8000),
@strData9 varchar(8000),
@strData10 varchar(8000),
@strData11 varchar(8000),
@strData12 varchar(8000),
@strData13 varchar(8000),
@strData14 varchar(8000),
@strData15 varchar(8000),
@strData16 varchar(8000),
@strData17 varchar(8000),
@strData18 varchar(8000),
@strData19 varchar(8000),
@strData20 varchar(8000)
None of the code in this procedure or from the calling methods looked any better. The data going into the varchar(8000) fields was delimited with a grab bag combination of special characters. Which was then pealed apart using cursors.
|
|
|
|
|
I think computer viruses should count as life. I think it says something about human nature that the only form of life we have created so far is purely destructive. We've created life in our own image.
Stephen Hawking
|
|
|
|