throws Exception bad practice?
<p>I'm reviewing code for a colleague and I encounter a piece of code similar to this:</p>

<pre><code>public X Foo1(Y y) throws Exception {
    X result = new X(y);
    result.Foo2();
    return result;
}
</code></pre>

<p>I believe there is no need for <code>throws Exception</code> part but I'm having difficulties justifying this. It might make sense if it was more specific <code>Exception</code>(<code>FileNotFound</code>, <code>NoMemory</code> etc.) but as it is I think it is unnecessary. Can someone give me some reasons what problems this can cause and why it is bad practice? Or is this code ok?</p>
