i'm going to knock your socks off this week people.
(next week, i'm
going to knock your socks
and
your shoes off.. but let's live for the
moment)
this week's prize package includes
- A leather Kenneth Cole PDA holder
- A leather business card holder
- A watch (slight issue with keeping time but doesn't actually keep
it from being a must-have fashion accessory for the fall)
- A t-shirt
- 3 Java collector's pins (hottest thing going in Olympic village)
- A bunch of Duke on a surf board (temporary) tatoos
- A pen with one of those clips things that rock climbers use (in
case you wanted to jot something down on your way up that big rock in
Yosemite which i can't excatly remember the name of right at this
minute.)
- A card that you can use to get a free ringtone on java.com
- Java Powered stickers on for your Java Powered phone (get on the
horn and tell those carriers that you want to see the Java logo on your
Java Powered phone. That the coolest thing about your phone is the fact
that it's running Java. And since it's already running Java, you want
your logo, damn it!).

- And last but certainly not least, a must-have foam "armchair"
that you can use to cradel that Java Powered phone on your desk. (or
give to your kids; great Barbie chairs.)
oh, can you even believe it?!
but wait, there's more... we got a bonified puzzler this week people.
Straight from the personal email account(s) of
Dr. Josh
Bloch and
Dr. Neal
Gafter addressed to me.
that's right, me.
Be still my beating heart.
And we're going to get straight to it...
right after I remind you:
- To buy Dr.
Josh's Book, Effective Java
-- it's as near and dear to the hearts of
Java developers as Dianetics is to people who follow Scientology
- To download
Tiger. Beat the rush.
- *Friday
Free Stuff is not a contest. It's me giving away stuff
that I personally own to somebody I choose. I pay for shipping that
stamps that I buy at the post office. Sun employees can play but they can't win* the prize*
Here's our puzzler. Post your answers to the comments of this blog
entry for your chance to win* the fabulous prize package shipped
directly to you free of charge.
The idea behind private members
(methods, fields, types) is that they're simply implementation details:
the implementor of a class can feel free to add new ones and change or
remove old ones without fear of harming clients of the class. In
geek-speak, private members are fully encapsulated by the class
that contains them.
Unfortunately, there are a few chinks in
the armor. For example, serialization can break this encapsulation. As
explained in Effective Java Items 54 and 55, making a class
serializable and accepting the default serialized form causes the
class’s private private instance fields to become part of its exported
API. Changes in the private represntation can then lead to runtime
exceptions or erratic behavior.
But what about compile-time errors? Can
you cause a client of a final class to fail to compile simply by adding
a private member to the class? (By "client" we mean a class in a
separate package that invokes public constructors or methods of the
class, or accesses its public fields.)
you know what to do.
happy Friday!!
mary