GNU bug report logs - #22241
25.0.50; etags Ruby parser problems

Previous Next

Package: emacs;

Reported by: Dmitry Gutov <dgutov <at> yandex.ru>

Date: Sat, 26 Dec 2015 04:00:02 UTC

Severity: normal

Found in version 25.0.50

Done: Dmitry Gutov <dgutov <at> yandex.ru>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: 22241 <at> debbugs.gnu.org
Subject: bug#22241: 25.0.50; etags Ruby parser problems
Date: Sun, 24 Jan 2016 17:44:44 +0200
> Cc: 22241 <at> debbugs.gnu.org
> From: Dmitry Gutov <dgutov <at> yandex.ru>
> Date: Sun, 24 Jan 2016 00:43:21 +0300
> 
> On 01/23/2016 11:48 PM, Eli Zaretskii wrote:
> 
> >> ^[ \t]([A-Z][a-z0-9_])[ \t]*=[ \t]*
> 
>                          ^ I missed a * there.
> 
> >> ? Then record the first group, and simply don't look at what's being
> >> assigned.
> >
> > That's possible, but is it good enough?  Does the above regexp
> > necessarily mean it's a constant?
> 
> I think so. The important point is that its name begins with a capital 
> letter.
> 
> And we should probably recognize assignments like these:
> 
> ModuleExample::CONSTANT = 5
> 
> The qualified name "ModuleExample::CONSTANT" if at the top level, 
> unqualified name is "CONSTANT". When inside classes, modules or methods, 
> only record the unqualified name; maybe disregard these assignments when 
> inside methods altogether.

OK, thanks.  I will see what I can do with this.




This bug report was last modified 9 years and 161 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.