Re: Some same exceptions used in a given file
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Eric Sosman <esosman@ieee-dot-org.invalid> writes:
On 4/23/2011 1:08 PM, Merciadri Luca wrote:
In some of my code files, I've got the following catch block
==
catch (IOException cantOpenFile)
{
System.err.println("Can't open " + inputFilename + ".");
System.exit(1);
}
==
more than once, but at different places in the file. Is it possible to
define this somewhere so that I can directly catch the exception with
the two given commands? (Just as one would define his own exception.)
Could you give an example of what you're trying to do? (The
above isn't sufficiently informative.)
Thanks for the answers. Sure I can provide more details. Let us
consider the following constructor:
==
public FileStream ()
{
try
{
outputFile = new BufferedWriter(new FileWriter("hello.txt"));
}
catch (IOException cantWriteInFile)
{
System.out.println("Impossible to write (in) hello.txt.");
System.exit(1);
}
}
==
You saw that I had to catch an IOException, as expected when dealing
with a BufferedWriter.
Now, in a function of the same class of the constructor (class
FileStream), I need to write in the output file. As a result, I've got
==
public void write (String outputText)
{
try
{
outputFile.write(outputText);
outputFile.close();
}
catch (IOException cantWriteInFile)
{
System.out.println("Impossible to write (in) hello.txt.");
System.exit(1);
}
}
==
You directly notice that the two catch blocks are identical. As a
result, I'd like to do something like this (in pseudocode):
==
public FileStream ()
{
try
{
outputFile = new BufferedWriter(new FileWriter("hello.txt"));
}
catch (IOException cantWriteInFile);
}
==
then, later in the file:
==
public void write (String outputText)
{
try
{
outputFile.write(outputText);
outputFile.close();
}
catch (IOException cantWriteInFile);
}
==
where IOException cantWriteInFile is defined in the class as
==
System.out.println("Impossible to write (in) hello.txt.");
System.exit(1);
==
Is there a way to do this? It looks terribly bad to have the same
catch code in two different methods.
- --
Merciadri Luca
See http://www.student.montefiore.ulg.ac.be/~merciadri/
- --
It is better to die on one's feet than live on one's knees.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iEYEARECAAYFAk2zS/gACgkQM0LLzLt8MhwA0wCfRH1BsrILdbrVlec2DT9N1owH
OcgAnjDtla3lWuZNWkLR/1iXV6kHp/6h
=UvEN
-----END PGP SIGNATURE-----