public inbox for cocci@systeme.lip6.fr
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Handling of omitted data type specification?
Date: Mon, 08 Apr 2013 23:14:45 +0200	[thread overview]
Message-ID: <51633345.6060103@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1304081655220.1963@hadrien>

> In the previous fix that I made, I just caused the missing type,
> which was hidden under a macro, to make the match fail.

How do you think about to make this detail configurable?


> In this case, though perhaps you would prefer T to be bound to int?

Does the C programming language specify that integers are used as the default
data type (or if modifiers are used)?
http://stackoverflow.com/questions/2099830/unsigned-keyword-in-c#2099873
https://www.cs50.net/resources/cppreference.com/data_types.html
http://en.cppreference.com/w/cpp/language/types


> That might cause some problemes, though, because it is not a real "int"
> in the source code...

Does the semantic patch language support to filter for omitted data types?

Would you like to distinguish the use case if this item was just forgotten or
intentionally omitted?

Regards,
Markus

  parent reply	other threads:[~2013-04-08 21:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1364983201.25969.cocci@systeme.lip6.fr>
2013-04-08 14:29 ` [Cocci] Analysis for Linux source files Nic Volanschi (R&D)
2013-04-08 14:54   ` Julia Lawall
2013-04-08 14:56   ` Julia Lawall
2013-04-08 15:05     ` Nic Volanschi (R&D)
2013-04-15 14:29       ` Julia Lawall
2013-04-08 21:14     ` SF Markus Elfring [this message]
2013-04-09  5:19       ` [Cocci] Handling of omitted data type specification? 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=51633345.6060103@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