From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Road map after Coccinelle 1.0.0-rc21?
Date: Mon, 14 Apr 2014 16:41:55 +0200 [thread overview]
Message-ID: <534BF3B3.90007@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1404141634180.2591@hadrien>
> There was some proble about really huge regular expressions, which I think
> must be a library problem, not a Coccinelle problem, so I don't plan to do
> anything about it.
Did you eventually reproduce exceptions from the handling of a bit smaller
alternation in a SmPL constraint once more?
How are the chances that if this one would be fixed that the bigger filter
pattern will also work?
Regards,
Markus
next prev parent reply other threads:[~2014-04-14 14:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 12:05 [Cocci] Coccinelle 1.0.0-rc21 Julia Lawall
2014-04-14 13:08 ` [Cocci] Road map after Coccinelle 1.0.0-rc21? SF Markus Elfring
2014-04-14 13:27 ` Julia Lawall
2014-04-14 13:45 ` SF Markus Elfring
2014-04-14 14:22 ` Julia Lawall
2014-04-14 14:30 ` SF Markus Elfring
2014-04-14 14:35 ` Julia Lawall
2014-04-14 14:41 ` SF Markus Elfring [this message]
2014-04-14 15:27 ` Julia Lawall
2014-04-14 16:45 ` SF Markus Elfring
2014-04-15 5:22 ` Julia Lawall
2014-04-15 6:31 ` SF Markus Elfring
2014-04-15 7:10 ` Julia Lawall
2014-04-15 7:36 ` SF Markus Elfring
2014-04-15 8:01 ` Julia Lawall
2014-04-15 8:40 ` [Cocci] Relevance of some regular expressions in SmPL SF Markus Elfring
2014-04-15 8:50 ` Julia Lawall
2014-04-15 9:01 ` SF Markus Elfring
2014-04-20 17:56 ` [Cocci] Road map after Coccinelle 1.0.0-rc21? Julia Lawall
2014-04-20 19:18 ` SF Markus Elfring
2014-04-14 16:26 ` [Cocci] Coccinelle 1.0.0-rc21: Clarification for "coccilib.elems"? SF Markus Elfring
2014-04-14 19:48 ` SF Markus Elfring
2014-04-14 16:52 ` [Cocci] Coccinelle 1.0.0-rc21 Derek M Jones
2014-04-15 5:23 ` 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=534BF3B3.90007@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox