[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#22241: 25.0.50; etags Ruby parser problems
From: |
Eli Zaretskii |
Subject: |
bug#22241: 25.0.50; etags Ruby parser problems |
Date: |
Wed, 03 Feb 2016 18:26:04 +0200 |
> Cc: 22241@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Tue, 2 Feb 2016 22:59:35 +0300
>
> >> If there's a comma at the end of the current line, the argument list
> >> continues on the next one.
> >
> > ...this. If supporting such split definitions is important, it will
> > need a slightly more complex code.
>
> It's basically a multiline function call. Not sure how frequently that
> is used with attr_* in practice, but in our big project at work, just
> one out of 190 attr_* declarations is multiline.
>
> So, it happens, but in the vast majority of cases the arguments stay on
> one line. Some projects (like Rails) choose to make several calls
> instead, as a stylistic choice.
>
> I can't really say yet if the lack of support for multiline calls is a
> significant problem, but it is an omission.
>
> Whether to implement it now, or close this bug and wait until another
> bug report, is up to you.
I implemented that now.
- bug#22241: 25.0.50; etags Ruby parser problems, Dmitry Gutov, 2016/02/01
- bug#22241: 25.0.50; etags Ruby parser problems, Dmitry Gutov, 2016/02/01
- bug#22241: 25.0.50; etags Ruby parser problems, Eli Zaretskii, 2016/02/02
- bug#22241: 25.0.50; etags Ruby parser problems, Dmitry Gutov, 2016/02/02
- bug#22241: 25.0.50; etags Ruby parser problems,
Eli Zaretskii <=
- bug#22241: 25.0.50; etags Ruby parser problems, Dmitry Gutov, 2016/02/03
- bug#22241: 25.0.50; etags Ruby parser problems, Eli Zaretskii, 2016/02/03
- bug#22241: 25.0.50; etags Ruby parser problems, Dmitry Gutov, 2016/02/04
- bug#22241: 25.0.50; etags Ruby parser problems, Eli Zaretskii, 2016/02/04
- bug#22241: 25.0.50; etags Ruby parser problems, Dmitry Gutov, 2016/02/04