John Austin wrote:
Isn't allocation the only unseen part of construction ? Everything
else is visible in the code and surely a few assignments are never
expensive. Any other expensive operations will stand out in
measurements of code execution.
That's correct. However, the article seemed to shout
On Fri, 2004-02-20 at 15:46, J.Pietschmann wrote:
*bg*
Twenty years ago, I had to work on a 8008 driven computer
with 4k RAM and 12k ROM. That's enough to run a program
which nicely prints formatted and justified text (25 lines
a 80 characters). We went a lng way since then.
I went to a
John Austin wrote:
I noticed this artcle on Developer Works:
Java theory and practice: Garbage collection and performance
http://www-106.ibm.com/developerworks/library/j-jtp01274.html
Something to read on Thursday.
Nice read, however, they don't talk about constructors. There
are still arguments
On Thu, 2004-02-19 at 17:53, J.Pietschmann wrote:
John Austin wrote:
I noticed this artcle on Developer Works:
Java theory and practice: Garbage collection and performance
http://www-106.ibm.com/developerworks/library/j-jtp01274.html
Something to read on Thursday.
Nice read,
I noticed this artcle on Developer Works:
Java theory and practice: Garbage collection and performance
http://www-106.ibm.com/developerworks/library/j-jtp01274.html
Something to read on Thursday.
--
John Austin [EMAIL PROTECTED]
