Is there an advantage to using static global work variables?
<p>This may be picking at nits, but are there any time/memory efficiencies in using global static fields for throwaway work variables?  Given the trivial example:</p>

<pre><code>class theClass {

private static GregorianCalendar wkCal;
private static int wkTimes1;
private static int wkTimes2;
private static int wkTimes3;
private static StringBuilder wkSb = new StringBuilder();

void aMethod(int n) {
    wkTimes1 = n * 1;
    wkTimes2 = n * 2;
    wkTimes3 = n * 3;
    wkCal = new GregorianCalendar();
    wkSb.setLength(0);
    wkSb.append("A string"); 
    // And so on...
}
}
</code></pre>

<p>This snippet has the potential to be instantiated many times (> 3000) and aMethod being used many times per instantiation. Additionally, the wk prefixed fields will be used in other methods and are designed to hold temporary values used only for intermediate calculations.</p>

<p>The way I see it, if you heed the usual caveats about using global variables, this saves memory and time.  </p>
