From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Searching for pass-through functions
Date: Sun, 05 Oct 2014 19:09:20 +0200 [thread overview]
Message-ID: <54317B40.3010305@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1410051900090.2022@localhost6.localdomain6>
> At least the first one has a lot of nested loops and conditionals.
> This is a case that Coccinelle does not handle well.
I am curious if the chances will increase to improve this detail in the future.
>> - Can the software situation be improved for the other two issues?
>
> Probably for the lexer. Perhaps not for the case of inconsistent paths.
> Again that relates to a particular kind of code structure.
I am also curious about how the software development will be continued for these
update candidates.
Regards,
Markus
next prev parent reply other threads:[~2014-10-05 17:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 17:49 [Cocci] Searching for pass-through functions SF Markus Elfring
2014-10-04 19:17 ` Julia Lawall
2014-10-04 20:22 ` SF Markus Elfring
2014-10-04 21:32 ` Julia Lawall
2014-10-05 6:48 ` SF Markus Elfring
2014-10-05 9:39 ` Julia Lawall
2014-10-05 13:15 ` SF Markus Elfring
2014-10-05 11:45 ` SF Markus Elfring
2014-10-05 11:48 ` Julia Lawall
2014-10-05 12:15 ` SF Markus Elfring
2014-10-05 15:33 ` Julia Lawall
2014-10-05 16:38 ` SF Markus Elfring
2014-10-05 16:42 ` Julia Lawall
2014-10-05 16:55 ` SF Markus Elfring
2014-10-05 17:01 ` Julia Lawall
2014-10-05 17:09 ` SF Markus Elfring [this message]
2014-10-05 18:37 ` SF Markus Elfring
2014-10-08 11:40 ` SF Markus Elfring
2014-10-08 11:51 ` Julia Lawall
2014-10-08 12:01 ` SF Markus Elfring
2014-10-08 12:08 ` Julia Lawall
2014-10-08 12:20 ` SF Markus Elfring
2014-10-08 12:48 ` Julia Lawall
2014-10-08 13:01 ` SF Markus Elfring
2014-10-08 18:05 ` SF Markus Elfring
2014-10-09 5:37 ` Julia Lawall
2014-10-07 19:39 ` SF Markus Elfring
2014-10-07 19:44 ` Julia Lawall
2014-10-07 20:20 ` SF Markus Elfring
2014-10-07 20:26 ` Julia Lawall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54317B40.3010305@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=cocci@systeme.lip6.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.