OT: grammarian anality (Was: Memory Leak)
Lew wrote:
I think most of us know what "ko" (kilo-octets) means, and that it's actually
more precise than "kbytes", since a byte need not necessarily be eight bits
but an octet must be. Thanks for the elucidation anyway, though.
John B. Matthews wrote:
Aha! Thanks. I overlooked the correct interpretation, but I always enjoy
learning something new:
You're my hero! Seriously, you have a great attitude.
<http://en.wikipedia.org/wiki/Octet_(computing)>
This and a matching Wikipedia article on "byte" were recent reading for me,
and I looked them up again as I wrote my post cited above. I, too, had gotten
so used to eight-bit bytes that I'd completely forgotten about other widths
until I read those articles a little while ago.
The implementation dependence of bits-per-byte is fundamental in Ada
(System.Storage_Unit), so I should know better:
<http://www.adaic.com/standards/05rm/html/RM-13-7.html>
Even with the best intentions, Murphry's Law applies:
<http://home.pacific.net.au/%7Ebangsund/muphry.htm> [sic]
With apologies to the OP, I look forward to learning what was leaking
from his applet.
I've been chastised myself many times for correcting others' English. I do
insist that spelling the pronoun "I" correctly is mandatory practice for any
porgrammer who works with a case-sensitive language like Java and (at least
occasionally) writes in English. Otherwise I agree with the chastisers that
it's best to give folks a break, unless they're born-and-raised Americans in
which case correct us mercilessly. Except for textspeek - there's no excuse
for that in a professional forum. OK, chastisers, I'm 80% cured, and I'm
afraid you're just going to have to throw your hands up over the last 20%.
To the OP: John's quote of your post with corrections embedded was actually a
very positive thing. He gave a thourough rephrase in more formal English of
what you said, giving you the opportunity to ensure that we understood you
correctly and hopefully helping you with English. I hope you'd do the same
for any of us who attempt to speak in French as a foreign language.
As to your problem:
How could [I] force [the] browser to free memory when [I] leave [the]
applet page?
Isn't there an applet 'destroy()' method that can be invoked on page exit? I
suck at applets, but there's an Andrew Thompson in this newsgroup who hates
applets and seems to know exactly how to make them work as no one else can.
He'll urge you to use Java Web Start instead, for the love of Pete! then
reveal the innards of how to get IE and mozilla-esque browsers in their
separate ways to sing your song. While correcting your grammar and urging you
to provide an SSCCE. I hope he chimes in on this thread.
--
Lew
It's like being in the audience when the performer unexpectedly says, "We have
a special guest in the room tonight! Shine the spotlight on and give a warm
welcome to ...!" and it's you.