Re: Generics and forName()

Jacob wrote:

> The problem is that in my organization we treat warnings as errors and
> the above simply isn't doable within such a regime.

Ha ha! Then you loose!

I'm not sure about the particular example you mention -- I don't know a
(working) way to avoid the warning myself, but that doesn't mean there isn't
one[*].

But the real problem here is not javac, but the way your organisation works.
Find the person responsible for this absurd rule and fire him/her (and,
perhaps, also his/her manager). Or if the condition was imposed by a customer,
find the salesthing which accepted that clause in the contract and fire it.

-- chris

[*] Well, I suppose you could compile with -source 1.4



.

Relevant Pages

  • Re: Firing without the clip in
    ... aka the Jericho to the Isralei Army (imported by Magnum Research). ... It comes with clear warnings that it WILL ... fire with the magazine out and a round in the chamber. ...
    (rec.guns)
  • Event ID:4098 Source:Event System Catagory Firing Agent
    ... Xseries running windows 2000 server, ... were just warnings we wouldn't worry to much about it, ... minutes from the time you hit Ctrl+Alt+Delete to full logon, ... The COM+ Event System failed to fire the Logon method on subscription ...
    (microsoft.public.win2000.general)
  • Simple compiled regexp not working
    ... use strict; use warnings; ... The way I read perlop, both print statements should fire, as they ...
    (comp.lang.perl.misc)