On 26.11.2008, at 19:58, Rich Morin wrote:
> Unless your code gets brought into play by the shebang line, my guess > is that it has to wait until the "load 'merb'" line runs. This is > _after_ the "require 'rubygems'", so the information I need (on the > classes and methods that Ruby itself provides) has already been > contaminated. True? Do you need that information out of curiosity or there is a particular need? If you want to have a complete call stack of Merb load, including calls to C libraries, you may need to use gdb or dtrace. Ruby has great introspection capabilities but to observe the whole process you need external tools. MK --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "merb" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/merb?hl=en -~----------~----~----~----~------~----~------~--~---
