From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] recvmmsg(2) system call tests
Date: Mon, 5 Nov 2018 11:06:36 +0100 [thread overview]
Message-ID: <20181105100624.GB8687@rei> (raw)
In-Reply-To: <9aae07a5-3a03-9da7-d8fd-0326fe3f4cc5@google.com>
Hi!
> About this statemement that you made:
>
> "Function signatures aren't needed when used just in one file."
>
> To whch I replied:
>
> "ARE required unless you reorganize you code to be all in the order
> of called functions preceding called functions"
>
> To which you replied:
>
> "Actually neither of that is true"
I actually answered only the part about 'static' being useless. Sorry
for not being clear on that.
> If you don't use prototypes you do have to reorganize the functions in
> the order they are called.
That is indeed true.
> Are you really questioning that? I don't want to have to explain that
> unless you don't understand why prototypes are required in some cases.
Not at all.
> If you are not questioning that. Are you ok with me using prototypes?
I do prefer to organize tests so that we don't have to use them, but I
can live with code that does not follow that as well.
> I don't mind adding static, but do realize that that will indeed mean
> that in some compilation systems the sysmbols won't be in the symbol
> table and will make debugging harder. I don't care if you question this
> statment, don't have time to explain that.
For modern enough compilers and debuggers this is not true. Ancient
tooling may loose some debugging information when functions are inlined
though.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2018-11-05 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 23:57 [LTP] recvmmsg(2) system call tests Ramon Pantin
2018-11-01 11:38 ` Petr Vorel
2018-11-02 0:13 ` Ramon Pantin
2018-11-02 10:52 ` Cyril Hrubis
2018-11-03 22:16 ` Ramon Pantin
2018-11-03 22:18 ` Ramon Pantin
2018-11-05 9:40 ` Cyril Hrubis
2018-11-05 18:35 ` Ramon Pantin
2018-11-06 10:25 ` Cyril Hrubis
2018-11-03 22:37 ` Ramon Pantin
2018-11-05 10:06 ` Cyril Hrubis [this message]
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=20181105100624.GB8687@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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