Looks like you're right. I don't think HexDump is used by the core API
however (thank goodness). It's used for the biff viewer.
I'll fix this up in the branch and the trunk.
Many thanks,
Glen Stampoultzis
At 06:09 PM 30/06/2003, you wrote:
>While skimming through some classes I noticed HexDump looks thread-unsafe as
>well...any reason why the two one-arg dump() methods use instance variables?
>and for that matter, are'nt they identical to the toHex() methods which are
>safe?
>
>Amichai
>
>----- Original Message -----
>From: "Andrew C. Oliver" <acoliver@apache.org>
>To: "POI Developers List" <poi-dev@jakarta.apache.org>
>Sent: Friday, June 27, 2003 12:19 AM
>Subject: Everyone experiencing concurrency issues
>
>
> > If everyone who experienced concurrency issues would please test, we'd
> > appreciate it.
> >
> > Secondly, assistance in profiling POI and especially HSSF would be GREATLY
> > appreciated. This is desired in particular between the last release and
> > when this fix was applied but in general as well. Anyone who is willing
>to
> > regularly profile things and analyze where memory and performance issues
>can
> > be tackled would be much loved.
> >
> > Now if I can find a decent java profiling tool for OS X, life will be good
> > :-)
> >
> > -Andy
> > --
> > Andrew C. Oliver
> > http://www.superlinksoftware.com/poi.jsp
> > Custom enhancements and Commercial Implementation for Jakarta POI
> >
> > http://jakarta.apache.org/poi
> > For Java and Excel, Got POI?
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: poi-dev-help@jakarta.apache.org
> >
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: poi-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: poi-dev-help@jakarta.apache.org
Glen Stampoultzis
gstamp@iinet.net.au
http://members.iinet.net.au/~gstamp/glen/
|