Try/catch block...

[_Vitor Garcia_]

Maybe the file was in use :laugh:

[spencepk]

Huh... why bother?

[Thomas Daniels]

When I was programming that, I thought: "It's in a catch block, then it can't throw an error!" X|

ProgramFOX

[Gary R Wheeler]

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;

[RafagaX]

Mmmm... you seem determined to read that file, is it important?

CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...

[Thomas Daniels]

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

[bkebamc]

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 }

[jnlt]

Timed out first time, then worked the second time?

[PhilLenoir]

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.

[Member 7711917]

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
}

[H Brydon]

:laugh: :-D :) Ha ha that's awesome! A fiver for you!

-- Harvey

[Bernhard Hiller]

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?

[lukeer]

Your'e doing it wrong! (Even catch blocks end in curly braces.)

Ciao, luker

[KP Lee]

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;
    }

[Brisingr Aerowing]

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.

:doh: 2.0.82.7292 SP6a

[kakan]

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

[_beauw_]

If you're using Windows, then the file is almost always in use.