Welcome to the Lounge

CodeWraith wrote:

What to do with an exception that does not hurt, can't be prevented, nor meaningfully handled?

CodeWraith wrote:

What to do with an exception that does not hurt, can't be prevented, nor meaningfully handled?

Dean Roddey wrote:

To be fair, general purpose code doesn't care what the error is in the bulk of cases. It wants to clean up and pass it up the chain to something that has some problem domain understanding of what is going on.

Gary Wheeler wrote:

Happy now?

using System;
using System.Runtime.CompilerServices;
using System.Text;

namespace YouMama
{
    // C# >= 5
    public static class MotherOfAllExceptionHandlersExtensions
    {
        public static string ThrowToMama(this Exception ex, bool doLog = true,
            [CallerMemberName] string yoName = null, 
            [CallerFilePath] string yoFilePath = null, 
            [CallerLineNumber] int yoLine = -1)
        {
            StringBuilder sb = new StringBuilder();

            //  whip, blend, puree ... to taste

            string log = sb.ToString();

            if (doLog)
            {
                Logger(log);
            }

            return log;
        }

        public static void Logger(string data)
        {
            // whatever
        }
    }
}
    
// use example
private void button1_Click(object sender, EventArgs e)
{
    int y = 1;

    try
    {
        int x = 1 / (y - 1);
    }
    catch (Exception ex)
    {
        ex.ThrowToMama();
    }
}

catch (Exception ex) {
    string tmp = ex.Message;
}

TNCaver wrote:

Which is the solution Marc asked for in the OP, n'est-ce pas?

Marc Clifton wrote:

Look, if you're going to catch an exception, at least give it a variable so in the debugger I can see what the exception is