From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Transformations for implementations of functions without explicit return type
Date: Sun, 28 Sep 2014 16:28:34 +0200 [thread overview]
Message-ID: <54281B12.6030309@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1409281603340.2394@hadrien>
> The lack of a return type is not supported for K&R functions.
That is a pity.
Now it seems that a function like "my_free" could only be adjusted after
a patch will be applied from my bug report.
https://github.com/gvelez17/glimpse/issues/6
How do you think about the possibility to transform more such
implementation details from a Kernighan/Ritchie coding style to a
current C standard approach?
Regards,
Markus
next prev parent reply other threads:[~2014-09-28 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 5:30 [Cocci] Transformations for implementations of functions without explicit return type SF Markus Elfring
2014-09-28 9:54 ` Julia Lawall
2014-09-28 13:44 ` SF Markus Elfring
[not found] ` <alpine.DEB.2.10.1409281603340.2394@hadrien>
2014-09-28 14:28 ` SF Markus Elfring [this message]
[not found] ` <alpine.DEB.2.10.1409281700330.2394@hadrien>
2014-09-28 15:53 ` [Cocci] Conversion of coding style "K&R" to newer C standard approaches? 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=54281B12.6030309@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