http://www.codebenders.com/code-cat/preventing-recursion-in-ruby/ Agile Software Developers Thu, 19 Apr 2012 17:26:00 +0000 hourly 1 http://wordpress.org/?v=3.0.4 http://www.codebenders.com/code-cat/preventing-recursion-in-ruby/#comment-286 Karol Bucek Mon, 06 Feb 2012 09:34:00 +0000 http://www.codebenders.com/?p=1135#comment-286 I already realized my mistake (and updated the post), I originally thought it's thread locals here are unnecessary and can be avoided but in general per thread state is the "safest" way to go to prevent recursion. I already realized my mistake (and updated the post), I originally thought it’s thread locals here are unnecessary and can be avoided but in general per thread state is the “safest” way to go to prevent recursion.

]]> http://www.codebenders.com/code-cat/preventing-recursion-in-ruby/#comment-285 Anonymous Sun, 05 Feb 2012 19:22:00 +0000 http://www.codebenders.com/?p=1135#comment-285 Where does the "abuse" come in? (and Avdi responded to the necessity already) Where does the “abuse” come in? (and Avdi responded to the necessity already)

]]> http://www.codebenders.com/code-cat/preventing-recursion-in-ruby/#comment-284 Anonymous Sun, 05 Feb 2012 19:21:00 +0000 http://www.codebenders.com/?p=1135#comment-284 nice piece of code nice piece of code

]]> http://www.codebenders.com/code-cat/preventing-recursion-in-ruby/#comment-281 Avdi Grimm Fri, 03 Feb 2012 02:10:00 +0000 http://www.codebenders.com/?p=1135#comment-281 As I replied on your blog, Thread.current is the only way to keep this both thread-safe and fiber-safe. Globally redefining methods temporarily is an extremely dangerous technique, because when it finally bites you it will be in the form of a bug that is impossible to reliably reproduce, and which gives little or no indications of its true origin. As I replied on your blog, Thread.current is the only way to keep this both thread-safe and fiber-safe. Globally redefining methods temporarily is an extremely dangerous technique, because when it finally bites you it will be in the form of a bug that is impossible to reliably reproduce, and which gives little or no indications of its true origin.

]]> http://www.codebenders.com/code-cat/preventing-recursion-in-ruby/#comment-280 Karol Bucek Thu, 02 Feb 2012 11:45:00 +0000 http://www.codebenders.com/?p=1135#comment-280 I think Thread.current is abused here and seems entirely unnecessary ... http://log.kares.org/2012/02/preventing-recursion-in-ruby-without.html I think Thread.current is abused here and seems entirely unnecessary …
http://log.kares.org/2012/02/preventing-recursion-in-ruby-without.html

]]> http://www.codebenders.com/code-cat/preventing-recursion-in-ruby/#comment-276 phiggy Wed, 01 Feb 2012 18:08:00 +0000 http://www.codebenders.com/?p=1135#comment-276 :__inspect_key__ is used in a few places in ruby's stdlib to do just what you're doing here, avoiding recursion during a call to #inspect in case an object refers to itself. :__inspect_key__ is used in a few places in ruby’s stdlib to do just what you’re doing here, avoiding recursion during a call to #inspect in case an object refers to itself.

]]> http://www.codebenders.com/code-cat/preventing-recursion-in-ruby/#comment-274 Alexander Paramonov Wed, 01 Feb 2012 14:18:00 +0000 http://www.codebenders.com/?p=1135#comment-274 Had similar problem some time ago with saving objects, that has relationships one to other. That was a reason i started this small gem https://github.com/AlexParamonov/save_queue that grow to something bigger than just recursion prevention. but not sure about it Tread safety. Will try to add tread-safe behavior to it. Thnx for post, Avdi Had similar problem some time ago with saving objects, that has relationships one to other. That was a reason i started this small gem https://github.com/AlexParamonov/save_queue that grow to something bigger than just recursion prevention.
but not sure about it Tread safety. Will try to add tread-safe behavior to it. Thnx for post, Avdi

]]>