Re: JTable help

nicholas.tripp@xxxxxxxxx wrote:
Awesome. Finally got it. Simple as leaving out the constructor for
the resultObject. Added that making it set the variable to null. No
more duplication! Thanks everybody for the help.

Setting variables to null is often a superstitious incantation with no real benefit. Some sources I've read claim it's harmful to heap management, which I have yet to believe. Most likely they are referring to the false sense of security that setting a variable to null can engender.

Which variable are you setting null, when?

--
Lew
.

Relevant Pages

  • Re: Dear Microsoft... Rebooting servers id NOT security..
    ... > | But I would be happy if MSoft matched my CISCO router, no duplication, ... > updates, no security issues..." ...
    (microsoft.public.windows.server.security)
  • security event logs in DC as well ? SOS
    ... I am shipping all the security and application event log from servers to a ... log agregation tool and i see some duplication of events from both the ... I am wondering if I even should ship the security evetn logs to the tool if ...
    (microsoft.public.windows.server.security)
  • Re: JTable help
    ... Simple as leaving out the constructor for ... the resultObject. ... more duplication! ...
    (comp.lang.java.help)