From: Johannes Berg <johannes@sipsolutions.net>
To: Markus Elfring <Markus.Elfring@web.de>,
Julia Lawall <julia.lawall@inria.fr>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] moving variable declarations up
Date: Thu, 18 Jun 2020 09:34:19 +0200 [thread overview]
Message-ID: <462123e6a9e7ec17b983dbb8d6f512280b08f450.camel@sipsolutions.net> (raw)
In-Reply-To: <b6ded75b-c4fe-dab6-b50a-d8ce55793b97@web.de>
On Thu, 2020-06-18 at 09:33 +0200, Markus Elfring wrote:
> > > You tried it out to move the variable “bar” which is an array of two pointers.
> >
> > Oops. I just mistyped that when transcribing it to email... It was 'u16
> > bar[2];' in the original.
>
> The intended absence of asterisks can make the clarification a bit easier.
> Are there still any software development challenges to consider for
> the movement of corresponding array sizes?
Well, it's surprising that it went there? And it doesn't compile?
johannes
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2020-06-18 7:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50990ed6-f5b7-c031-a5df-bdaa6863baa8@web.de>
2020-06-18 7:20 ` [Cocci] moving variable declarations up Johannes Berg
[not found] ` <b6ded75b-c4fe-dab6-b50a-d8ce55793b97@web.de>
2020-06-18 7:34 ` Johannes Berg [this message]
2020-06-17 20:54 Johannes Berg
2020-06-17 21:15 ` Julia Lawall
2020-06-17 21:19 ` Johannes Berg
2020-06-17 21:47 ` Johannes Berg
2020-06-18 15:25 ` Julia Lawall
2020-06-18 15:49 ` Julia Lawall
2020-06-18 5:59 ` Julia Lawall
2020-06-18 7:37 ` Johannes Berg
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=462123e6a9e7ec17b983dbb8d6f512280b08f450.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Markus.Elfring@web.de \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@inria.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).