exceptions upsurge control

there this, union cross-application upsurge control.

well, recently, i've opposing an engaging problem. generating nth value potentially (practically) spontaneity recursive sequence. sole algorithm atleast 10-15 smoke-stack references low during indicate succeeds. initial guess pitch successexception looked something (c#):

class successexception : exception
{
    open twine value
    { get; set; }

    open successexception(string value)
        : base()
    {
        value = value;
    }
}

then something this:

try
{
    walk_r(tree);
}
catch (successexception ex)
{
    outcome = ex.value;
}

then thoughts wandered behind here, where i've listened over over never exceptions upsurge control. there ever an excuse? structure something this, exercise it?