From: "Paolo \"Nusco\" Perrotta" Date: 2008-01-25T19:14:56+09:00 Subject: Re: Determine where a method is being called from? On Jan 23, 2:08 pm, Robert Klemme wrote: > I do not see how using #caller is a hack. This is probably in the eye of the beholder. To me, having the call stack as a single long string and parsing it to fish out the caller looks a bit hack-ish. It feels like #caller is supposed to be read by a human, not by code. >I was under the impression that Ben rather wanted a static analysis, >i.e. determine code coverage. This is next to impossible with a >dynamic language such as Ruby. Agreed. --- Paolo Perrotta Bologna, Italy