Bug#472053: Fwd: [Rxtx] gnu.io.RXTXPort discards exception silently if initialization fails

[Scott Howard]

---------- Forwarded message ----------
From: George H <george.dma at gmail.com>
Date: Wed, Jun 23, 2010 at 4:34 AM
Subject: Re: [Rxtx] gnu.io.RXTXPort discards exception silently if
initialization fails
To: "rxtx at qbang.org" <rxtx at qbang.org>


--
George H
george.dma at gmail.com



On Wed, Jun 23, 2010 at 11:17 AM, Michael Erskine <msemtd at googlemail.com> wrote:
> On 23 June 2010 06:38, Kustaa Nyholm <Kustaa.Nyholm at planmeca.com> wrote:
>>
>>> I did change the code to
>>>                try {
>>>                        z = new Zystem();
>>>                } catch ( Exception e ) {
>>>                        throw new Error(e.toString());
>>>                };
>>
>> Is there a reason why this could/should not be:
>>
>>
>>>                try {
>>>                        z = new Zystem();
>>>                } catch ( Throwable e ) {
>>>                        e.printStackTrace(System.err);
>>>                };
>
> Or even just let the exception bubble up and kill whatever thread
> caused the class to load :)
>
> I vote for the removal of Zystem BTW!
>
> Regards,
> Michael Erskine.


I would prefer that an exception is thrown rather than the stack trace
be printed. If anyone is using loggers then it would be useful to
catch the exception and log it, rather than let it come out in the
error stream where no one might look.
_______________________________________________
Rxtx mailing list
Rxtx at qbang.org
http://mailman.qbang.org/mailman/listinfo/rxtx