Finally…
After spending a month and a half without access to the internet at home, (had to update the blog at university or at my friends house) I finally have the power. Expect a more updated blog in the next few days, and new categories (that will already have posts when launched) soon.
As you might have noticed there were some changes in terms of colors and link styles. The banner went from orange to a midnight blue, and the links/tables on the right also changed to blue, do you like it? I think it was a good change.
In other news… The Blog-X awards are up and running for the second time – Help choose the Best Independent Tech Blog of 2005 – Interesting enough, there's a blogspot.com candidate!
I have always wanted to say something like this… And the nominees are:
- Andy on Enterprise Software – andyhayler.blogspot.com
- Day in the Life of an Information Security Investigator – blogs.ittoolbox.com/security/investigator
- Gear Live – www.gearlive.com
- Gizmodo – www.gizmodo.com
- MuniWireless – www.muniwireless.com
- Oh Gizmo! – www.ohgizmo.com
- RealTechNews – www.realtechnews.com
- SmallBizTechnology.com – www.smallbiztechnology.com
- TechCruch – techcrunch.com
- TechNudge – www.technudge.com
Vote wisely at techweb.com, the winner will be world-wide-known at 16 December.
1 Comment
Other Links to this Post
RSS feed for comments on this post. TrackBack URI
By Jeremy Jones, January 29, 2007 @ 7:00 pm
The finally block always executes when the try block exits. This ensures that the finally block is executed even if an unexpected exception occurs. But finally is useful for more than just exception handling — it allows the programmer to avoid having cleanup code accidentally bypassed by a return, continue, or break. Putting cleanup code in a finally block is always a good practice, even when no exceptions are anticipated.
The try block of the writeList method that you’ve been working with here opens a PrintWriter. The program should close that stream before exiting the writeList method. This poses a somewhat complicated problem because writeList’s try block can exit in one of three ways.