From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] s_putc and Runes
Date: Mon, 5 Feb 2007 07:25:28 -0500 [thread overview]
Message-ID: <c9f33086c5db807ae01d9e4aa09fcc5f@coraid.com> (raw)
In-Reply-To: <ee9e417a0702041925l48432744kf91c8813a86c8bf5@mail.gmail.com>
i think this is a very powerful idea. although the
interface is high-level, and if you need to format a
structure, you need to write a print format, it results
in a good old char*, not a String*. the code that uses
String*s tends to have a fair percentage of code converting
between char* and String*. in a few cases i've removed
30 or 40 lines of code by converting from a String* to a
char*/*print because the conversion goo and String helper
functions and conversion goo were no longer needed.
- erik
On Sun Feb 4 22:25:53 EST 2007, rsc@swtch.com wrote:
> I confess that most of the time, when I need to write to a
> growable string buffer, I just use fmtstrinit, fmtprint, and fmtstrflush.
> It's just easier, and you get all the print verbs!
>
> Russ
next prev parent reply other threads:[~2007-02-05 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 2:41 Joel Salomon
2007-02-05 3:25 ` Russ Cox
2007-02-05 9:41 ` Bruce Ellis
2007-02-05 12:25 ` erik quanstrom [this message]
2007-02-05 19:52 ` Joel Salomon
2007-02-05 21:42 ` Paul Lalonde
2007-02-05 23:57 ` Joel Salomon
2007-02-06 6:23 ` Bruce Ellis
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=c9f33086c5db807ae01d9e4aa09fcc5f@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/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).