git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] diff: add ruby funcname pattern

From
Kevin Ballard <kevin@sb.org>
Date
Aug 2, 2008, 05:47 UTC
Message-ID
<C871A30D-F2AF-4385-ABD4-C57F474D7F01@sb.org>
In-Reply-To
<cb7bb73a0808012241s80a06fq1ac54a3350169f6c@mail.gmail.com>
On Aug 1, 2008, at 10:41 PM, Giuseppe Bilotta wrote:
Show 14 quoted lines
> On Sat, Aug 2, 2008 at 2:31 AM, Kevin Ballard <kevin@sb.org> wrote:
>>
>> As a Ruby user, the regex for the funcname looks fine to me.
>
> What is your opinion about the anonymous code blocks?
>
> I've been thinking that another possibility could be to have two ruby
> funcnames, a simpler one (the one I presented) that only has 'named'
> blocks, and a more thorough one that also matches up anonymous blocks.
> User could then choose which one to use in their code by having
> gitattributes such as *.rb diff=ruby or *.rb diff=ruby-full (or
> whatever else).
>
> I'm not sure this would be a sensible policy though.

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 think it's far simpler to stick with class/module/def.
-Kevin Ballard
-- 
Kevin Ballard
http://kevin.sb.org
kevin@sb.org
http://www.tildesoft.com
Previous: Giuseppe BilottaNext: Giuseppe Bilotta
Message 10 of 14 in “diff: add ruby funcname pattern”
  1. diff: add ruby funcname patternGiuseppe Bilotta, Jul 31, 2008
  2. Junio C HamanoAug 1, 2008
  3. Giuseppe BilottaAug 1, 2008
  4. Junio C HamanoAug 1, 2008
  5. Giuseppe BilottaAug 1, 2008
  6. Jeff KingAug 1, 2008
  7. Kevin BallardAug 2, 2008
  8. Junio C HamanoAug 2, 2008
  9. Giuseppe BilottaAug 2, 2008
  10. Kevin BallardAug 2, 2008
  11. Giuseppe BilottaAug 2, 2008
  12. Johannes SchindelinAug 2, 2008
  13. Giuseppe BilottaAug 2, 2008
  14. Lee MarlowAug 2, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.