From: Markus Elfring <Markus.Elfring@web.de>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Coccinelle <cocci@systeme.lip6.fr>
Subject: Re: [Cocci] Moving exception handling code to the end of a function implementation with SmPL?
Date: Thu, 27 Jun 2019 14:18:25 +0200 [thread overview]
Message-ID: <f84bb58a-916b-0d6b-64fd-7805bd8db827@web.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1906271332240.2627@hadrien>
> Maybe there are too many metavariable bindings.
Under which circumstances would such a situation really occur?
How do you think about my SmPL script example for the shown use case?
> You can try with the option --debug.
> Or if that doesn't help with the option --verbose-ctl-engine.
How can these parameters help to clarify undesirable run time characteristics?
Is it eventually easier to explain the following information?
elfring@Sonne:~/Projekte/Coccinelle/Probe> spatch --debug megaraid_sas-excerpt1.c ~/Projekte/Coccinelle/janitor/move_error_code_assignment_to_function_end1.cocci
…
replacement: already tagged token:
C code context
…
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-06-27 12:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 17:45 [Cocci] Moving exception handling code to the end of a function implementation with SmPL? Markus Elfring
2019-06-27 8:33 ` Markus Elfring
2019-06-27 11:33 ` Julia Lawall
2019-06-27 12:18 ` Markus Elfring [this message]
[not found] ` <alpine.DEB.2.21.1906271427250.2627@hadrien>
2019-06-27 12:45 ` Markus Elfring
2019-06-27 14:12 ` Markus Elfring
2019-06-27 14:54 ` Julia Lawall
2019-06-27 15:01 ` Markus Elfring
2019-10-31 12:27 ` Markus Elfring
2019-10-31 12:42 ` Julia Lawall
2019-10-31 13:50 ` Markus Elfring
2019-11-01 9:12 ` [Cocci] Checking the occurrence of trailing spaces in a semantic patch Markus Elfring
2019-11-01 9:38 ` Julia Lawall
2019-11-01 9:56 ` Markus Elfring
2019-11-01 11:50 ` Markus Elfring
2019-11-01 16:03 ` [Cocci] Checking code layout for adding jump targets with SmPL Markus Elfring
2019-11-01 16:12 ` Markus Elfring
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=f84bb58a-916b-0d6b-64fd-7805bd8db827@web.de \
--to=markus.elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@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;
as well as URLs for NNTP newsgroup(s).