|
From: | Dmitry Gutov |
Subject: | bug#22241: 25.0.50; etags Ruby parser problems |
Date: | Thu, 4 Feb 2016 11:24:52 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Thunderbird/44.0 |
On 02/04/2016 06:43 AM, Eli Zaretskii wrote:
IOW, skip the arguments that are not Ruby Symbols (don't start with a colon). The current implementation treats them the same.Yes, because etags is not supposed to do sensible things with syntactically incorrect programs.
This is syntactically correct: class C [:foo, :bar].each do |name| attr_reader name end end
I'm not sure I understand the rules, though: is the "no colon, don't tag" rule valid for any symbol following the attr_WHATEVER, or is that applicable only to the 2nd, 3rd, etc. symbols?
Any of the arguments.
IOW, what, if anything, should be tagged here: attr_reader foo
Just skip it as well.
[Prev in Thread] | Current Thread | [Next in Thread] |