Comments on: An idea for a ruby inspection tool http://blog.kriskemper.com/2008/10/25/an-idea-for-a-ruby-inspection-tool/ Thoughtworker, Agile Philosopher, Hero Thu, 11 Mar 2010 23:09:39 +0000 http://wordpress.org/?v=2.3.2 By: Phlip http://blog.kriskemper.com/2008/10/25/an-idea-for-a-ruby-inspection-tool/#comment-1221 Phlip Tue, 28 Oct 2008 16:03:26 +0000 http://blog.kriskemper.com/2008/10/25/an-idea-for-a-ruby-inspection-tool/#comment-1221 http://www.oreillynet.com/onlamp/blog/2008/05/dynamic_languages_vs_editors.html "Each time you run the tests, the editor should instrument your interpreter to extract type information. "Each test run should update a type library, containing the fully-derived type of every object found on every line of the source code, complete with the call stack that put it there." (-: http://www.oreillynet.com/onlamp/blog/2008/05/dynamic_languages_vs_editors.html

“Each time you run the tests, the editor should instrument your interpreter to extract type information.

“Each test run should update a type library, containing the fully-derived type of every object found on every line of the source code, complete with the call stack that put it there.”

(-:

]]> By: Kris Kemper http://blog.kriskemper.com/2008/10/25/an-idea-for-a-ruby-inspection-tool/#comment-1198 Kris Kemper Mon, 27 Oct 2008 12:50:51 +0000 http://blog.kriskemper.com/2008/10/25/an-idea-for-a-ruby-inspection-tool/#comment-1198 Thanks for the response Sidu. Do you perhaps have a list of methods/hooks that you think would be good to know about. Even if they are insufficient, I can always reduce the scope of the tool if I decide to build it. Thanks for the response Sidu. Do you perhaps have a list of methods/hooks that you think would be good to know about.

Even if they are insufficient, I can always reduce the scope of the tool if I decide to build it.

]]> By: Sidu http://blog.kriskemper.com/2008/10/25/an-idea-for-a-ruby-inspection-tool/#comment-1191 Sidu Mon, 27 Oct 2008 06:03:09 +0000 http://blog.kriskemper.com/2008/10/25/an-idea-for-a-ruby-inspection-tool/#comment-1191 I'd gotten started hacking code around this about six months ago, but found that the hooks Ruby offers don't suffice. It's also quite hard to intercept stuff in a manner which guarantees that the code being observed will be left unaffected. The only viable alternative AFAIK is to write a 'noisy' variant of the language itself, which though slow will have dozens more hooks and callbacks. Since C makes me want to run away and hide, I'd gotten started with JRuby, but stopped soon after for various reasons I no longer remember. I’d gotten started hacking code around this about six months ago, but found that the hooks Ruby offers don’t suffice.
It’s also quite hard to intercept stuff in a manner which guarantees that the code being observed will be left unaffected.
The only viable alternative AFAIK is to write a ‘noisy’ variant of the language itself, which though slow will have dozens more hooks and callbacks. Since C makes me want to run away and hide, I’d gotten started with JRuby, but stopped soon after for various reasons I no longer remember.

]]>