The Weird and The Wonderful

Function Wibble() As String
Dim sResult As String

On Local Error GoTo Fail

    'stuff goes here

done:
    Wibble = sResult
    Exit Function

Fail:
    LogError "Wibble", Err
    Resume done
End Function

_beauw_ wrote:

Even logging these failures in a production environment can impact other critical systems.

I are Troll

_beauw_ wrote:

Logging is I/O, which is a failure-prone and time-consuming category of operation.Consider what happens if I attempt to log inside of a deeply nested loop;

_beauw_ wrote:

There are .NET applications that control, or at least influence, real-time machinery.

_beauw_ wrote:

There are .NET programs that guide stock traders in real-time. Entering into an I/O routine is not always an acceptable response to failure in such environments

I are Troll

Kevin Drzycimski wrote:

they are world market leader

public void Demo_Show_Leaving_Trace_With_Exception()
{
    TracerConfig.Reset("console");
    SomeMethod();
}

void SomeMethod()
{
    using (Tracer t = new Tracer(myType, "SomeMethod"))
    {
        SomeOtherMethod();
    }
}

private void SomeOtherMethod()
{
    using (Tracer t = new Tracer(myType, "SomeOtherMethod"))
    {
        FaultyMethod();
    }
}

private void FaultyMethod()
{
    throw new NotImplementedException("Hi this a fault");
}

ChrisC(@ncmail) wrote:

Correct me if I'm wrong: using the EXISTS is a big no-no, right? Shouldn't you just do an extra left join (if necessary) and use that field instead of the EXISTS

ChrisC(@ncmail) wrote:

Correct me if I'm wrong: using the EXISTS is a big no-no, right? Shouldn't you just do an extra left join (if necessary) and use that field instead of the EXISTS?

ChrisC(@ncmail) wrote:

will often peform worse

ChrisC(@ncmail) wrote:

the work involved to do the join is greater