Mercurial > hg > Blog
changeset 96:57988fb9567c
The link to the java autoboxing problems was dead. Use a new one that describes the problem better.
| author | Dirk Olmes <dirk@xanthippe.ping.de> |
|---|---|
| date | Wed, 24 Jul 2019 08:29:42 +0200 |
| parents | ef1a3397bd90 |
| children | e99db3bc53c1 |
| files | content/Java/autoboxing.md |
| diffstat | 1 files changed, 1 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/content/Java/autoboxing.md Tue Jul 23 07:40:28 2019 +0200 +++ b/content/Java/autoboxing.md Wed Jul 24 08:29:42 2019 +0200 @@ -5,7 +5,7 @@ Autoboxing appeared first with JDK5 and lots of people go crazy about it. At first look it's a nice feature but the more you play with it the more I'm coming to the conclusion that the autoboxing implementation just sucks. -I will not rant about autoboxing pitfalls [that others have described already](http://www.certpal.com/blogs/2009/08/autoboxing-unboxing-gotchas/) but instead I'd like to point out my favourite autoboxing fail that alone is the reason not to use it: the `IntegerCache`. +I will not rant about autoboxing pitfalls [that others have described already](https://effective-java.com/2010/05/the-advantages-and-traps-of-autoboxing/) but instead I'd like to point out my favourite autoboxing fail that alone is the reason not to use it: the `IntegerCache`. Consider this code snippet: