From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Extending source code at file end with SmPL
Date: Tue, 2 Feb 2016 11:56:29 +0100 [thread overview]
Message-ID: <56B08B5D.3070301@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1602021111510.2494@hadrien>
>> How should the "file end" be expressed for the semantic patch language?
>
> There is no convenient way to express this. You could perhaps match all
> of the function definitions, find their line numbers, and put something
> after the last one.
Thanks for your feedback.
How are the chances to extend the SmPL capabilities for matching of
special positional constraints?
Are we looking for the support of functionality which is similar to the use
of the search operator "$" within regular expressions?
http://www.regular-expressions.info/anchors.html
Would it make sense to clarify any further extensions?
Regards,
Markus
next prev parent reply other threads:[~2016-02-02 10:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 9:55 [Cocci] Extending source code at file end with SmPL SF Markus Elfring
[not found] ` <alpine.DEB.2.10.1602021111510.2494@hadrien>
2016-02-02 10:56 ` SF Markus Elfring [this message]
[not found] ` <alpine.DEB.2.10.1602021205280.2494@hadrien>
2016-02-02 11:34 ` SF Markus Elfring
2016-02-02 11:37 ` Julia Lawall
2016-02-02 12:23 ` SF 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=56B08B5D.3070301@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.