From b3710c3fec4e45d238e408b49e0f7b1cd92ecd33 Mon Sep 17 00:00:00 2001 From: Janos Csikos Date: Thu, 21 Aug 2014 14:56:16 +0100 Subject: [PATCH] Update outdated external link to an article Fixing the broken link to "Extending built-in native objects. Evil or not?" article. --- chapters/metaprogramming/extending-built-in-objects.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/chapters/metaprogramming/extending-built-in-objects.md b/chapters/metaprogramming/extending-built-in-objects.md index 93b6b58..24eeab8 100644 --- a/chapters/metaprogramming/extending-built-in-objects.md +++ b/chapters/metaprogramming/extending-built-in-objects.md @@ -23,4 +23,4 @@ String::capitalize = () -> Objects in JavaScript (and thus, in CoffeeScript) have a prototype member that defines what member functions should be available on all objects based on that prototype. In CoffeeScript, you can access the prototype directly via the `::` operator. -**Note:** Although it's quite common in languages like Ruby, extending native objects is often considered bad practice in JavaScript (see: [Maintainable JavaScript: Don’t modify objects you don’t own](http://www.nczonline.net/blog/2010/03/02/maintainable-javascript-dont-modify-objects-you-down-own/); [Extending built-in native objects. Evil or not?](http://perfectionkills.com/extending-built-in-native-objects-evil-or-not/)). +**Note:** Although it's quite common in languages like Ruby, extending native objects is often considered bad practice in JavaScript (see: [Maintainable JavaScript: Don’t modify objects you don’t own](http://www.nczonline.net/blog/2010/03/02/maintainable-javascript-dont-modify-objects-you-down-own/); [Extending built-in native objects. Evil or not?](http://perfectionkills.com/extending-native-builtins/)).