From: "Torsten Bögershausen" <tboegi@web.de>
To: Ben Peart <Ben.Peart@microsoft.com>,
Ben Peart <peartben@gmail.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Cc: "christian.couder@gmail.com" <christian.couder@gmail.com>,
"larsxschneider@gmail.com" <larsxschneider@gmail.com>
Subject: Re: [PATCH v2 1/2] pkt-line: add packet_writel() and packet_read_line_gently()
Date: Thu, 30 Mar 2017 19:01:42 +0200 [thread overview]
Message-ID: <d8bb326c-6aec-9379-a5a6-051fa72f8d77@web.de> (raw)
In-Reply-To: <BL2PR03MB3237F4B369C0E00168D7291F4340@BL2PR03MB323.namprd03.prod.outlook.com>
On 30.03.17 18:01, Ben Peart wrote:
>> From: Torsten Bögershausen [mailto:tboegi@web.de]
>>
>>
>> Does this work ?
>> I would have expected
>> packet_writel(fd, "line one", "line two", "line n"), NULL;
Typo.
Should have been:
packet_writel(fd, "line one", "line two", "line n", NULL);
>>
>
> No, that's actually not valid C syntax.
>
>>>
>>> which requires the use of variable number of arguments. With your
>> proposal that convenience is lost as you have to create an array of strings
>> and pass that instead. The usage just isn't as simple as the current model.
>>>
>> What is wrong with
>>
>> int packet_write_fmt_gently(int fd, const char *fmt, ...) and we use it like
>> this:
>> if packet_write_fmt_gently(fd, "%s%s%s", "line one", "line two", "line n")
>>
>
> Packets are not just strings; see pkt-line.h for more details-
> but basically they are a length packet, followed by the data (in this particular case a string).
> The packet_writel function is a convenience function to write out a variable number of
> packetized strings followed by a flush packet.
> You're sample above would simply concatenate the three strings and then write a single packet.
> A very different outcome. :)
Got it.
next prev parent reply other threads:[~2017-03-30 17:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 15:27 [PATCH v2 0/2] Refactor the filter process code into a reusable module Ben Peart
2017-03-24 15:27 ` [PATCH v2 1/2] pkt-line: add packet_writel() and packet_read_line_gently() Ben Peart
2017-03-25 5:47 ` Torsten Bögershausen
2017-03-27 22:19 ` Ben Peart
2017-03-30 14:04 ` Torsten Bögershausen
2017-03-30 16:01 ` Ben Peart
2017-03-30 17:01 ` Torsten Bögershausen [this message]
2017-03-24 15:27 ` [PATCH v2 1/4] t7800: remove whitespace before redirect Ben Peart
2017-03-24 16:21 ` Ben Peart
2017-03-24 15:27 ` [PATCH v2 2/2] sub-process: refactor the filter process code into a reusable module Ben Peart
2017-03-27 18:59 ` Jonathan Tan
2017-03-27 23:54 ` Ben Peart
2017-03-24 15:27 ` [PATCH v2 2/4] t7800: cleanup cruft left behind by tests Ben Peart
2017-03-24 15:27 ` [PATCH v2 3/4] difftool: handle modified symlinks in dir-diff mode Ben Peart
2017-03-24 15:27 ` [PATCH v2 4/4] Git 2.12.1 Ben Peart
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d8bb326c-6aec-9379-a5a6-051fa72f8d77@web.de \
--to=tboegi@web.de \
--cc=Ben.Peart@microsoft.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=larsxschneider@gmail.com \
--cc=peartben@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).