On Sat, Aug 2, 2008 at 7:47 AM, Kevin Ballard <kevin@xxxxxx> wrote: > > If you're going to get into anonymous code blocks, you're going to have a > really tough time deciding which blocks are interesting and which aren't. > And as you stated before, without a stack-based approach, this could really > fall apart, as anonymous blocks are (almost) always going to be inside a > method. I was just looking for a libxdiff issue tracker but I couldn't find one, so I guess I'll ask the author directly about the possibility to implement such a thing. The matchit plugin for vim seems to manage (even user-defined) code blocks very well, even for multi-state blocks (if ... else ... end), using regexps; so maybe a reimplementation in C for libxdiff could be a solution. Of course, one wonders how much slower such an approach would be as opposed to the current "look back until the first matching line" solution ... -- Giuseppe "Oblomov" Bilotta -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
