# HG changeset patch # User Dirk Olmes # Date 1563949782 -7200 # Node ID 57988fb9567c51fa14cafc035578ca8978a642b5 # Parent ef1a3397bd9089e5f757c0247503929105e75ecc The link to the java autoboxing problems was dead. Use a new one that describes the problem better. diff -r ef1a3397bd90 -r 57988fb9567c content/Java/autoboxing.md --- 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: