At 21:05 +0200 11/26/08, Michael Klishin wrote: > Do you need that information out of curiosity or there is a > particular need?
My initial post gave a precis of this: > I'm playing around with merb, trying to add some infrastructure > for logging method calls, checking assertions, etc. My basic > plan, at this point, is as follows: > > * As soon as merb is run, walk ObjectSpace and record all of > the classes and methods that are defined at this point. > > * As soon as init.rb is run, walk ObjectSpace again and set > up "wrapper" methods for every "added" method (ie, ones > that were not recorded at start-up time). > > Also, set up a callback to set up a wrapper method for any > method that gets added after this point. Trying to add wrappers to all of Ruby's methods is problematic and probably not all that useful. So, I'm only adding wrappers to the methods that Merb brings into play. The only way I know to do this is to build a data structure, early on, that tells me which methods to skip in the wrapping process. Clues welcome... -r -- http://www.cfcl.com/rdm Rich Morin http://www.cfcl.com/rdm/resume [EMAIL PROTECTED] http://www.cfcl.com/rdm/weblog +1 650-873-7841 Technical editing and writing, programming, and web development --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
