Subject: Re: bug#22241: 25.0.50; etags Ruby parser problems

From: Eli Zaretskii <[email-masked]>
Date: Sat, 30 Jan 2016 12:52:33 +0200

> Cc: [email-masked]
> From: Dmitry Gutov <[email-masked]>
> Date: Sat, 23 Jan 2016 21:23:57 +0300
> 
> >> - "class << self" blocks are given a separate entry.
> >
> > What should be done instead?  Can't a class be named "<<"?
> 
> A class cannot be named "<<". You should not add that line to the index, 
> but record that the method definitions inside the following scope are 
> defined on the current class or module. These are equivalent:
> 
> class C
>    def self.foo
>    end
> end
> 
> class C
>    class << self
>      def foo
>      end
>    end
> end

What about the following snippet: what tags, if any, should it produce
for the 'class' line?

class << a
  def inspect
    '"bar"'
  end
end

Exuberant ctags doesn't produce anything for that line, FWIW.

Also, in the above example, what should be the class-qualified name of
'inspect'?

Thanks.