From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Re: [PATCH] Add private port structure, and move iconv descriptors there
Date: Wed, 27 Mar 2013 21:28:28 +0100 [thread overview]
Message-ID: <87ip4cr3ir.fsf@gnu.org> (raw)
In-Reply-To: <87d2uk62a0.fsf_-_@tines.lan> (Mark H. Weaver's message of "Wed, 27 Mar 2013 16:00:55 -0400")
Hi!
Mark H Weaver <mhw@netris.org> skribis:
> Here's a patch to add a private port structure. I moved both input_cd
> and output_cd there. I plan to create more patches on top of this very
> soon (BOM handling, more efficient per-port read options, maybe better
> EOF handling), so a prompt review would be very helpful.
Looks good to me, and definitely an improvement.
Nitpicking:
> +struct scm_t_port_private;
Please add a short comment above.
> + struct scm_t_port_private *internal;
> + void *reserved_for_future_use;
> } scm_t_port;
Likewise.
> +enum scm_t_port_encoding_type {
Likewise.
Also, brace on the next line.
I’d be tempted to remove ‘_t’ from the name since it’s a tag.
> +struct scm_t_port_private
Likewise.
> + enum scm_t_port_encoding_type encoding_type;
> + void *input_cd;
> + void *output_cd;
> +};
Ideally a comment saying what the fields represent.
Thanks!
Ludo’.
next prev parent reply other threads:[~2013-03-27 20:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 11:39 always O_BINARY? Andy Wingo
2013-02-24 12:08 ` Neil Jerram
2013-02-24 16:55 ` Mike Gran
2013-02-24 21:17 ` Ludovic Courtès
2013-02-28 3:24 ` Adding new information to scm_t_port (was Re: always O_BINARY?) Mark H Weaver
2013-02-28 8:53 ` Andy Wingo
2013-02-28 11:04 ` Ludovic Courtès
2013-02-28 13:09 ` Andy Wingo
2013-03-01 9:03 ` Ludovic Courtès
2013-03-05 18:55 ` Mark H Weaver
2013-03-27 20:00 ` [PATCH] Add private port structure, and move iconv descriptors there Mark H Weaver
2013-03-27 20:28 ` Ludovic Courtès [this message]
2013-03-27 20:51 ` Andy Wingo
2013-03-27 21:11 ` Mark H Weaver
2013-03-31 7:52 ` [PATCH] Add internal-only port structure; " Mark H Weaver
2013-03-31 13:20 ` Ludovic Courtès
2013-03-31 15:23 ` Mark H Weaver
2013-03-31 22:06 ` Ludovic Courtès
2013-04-01 18:57 ` Andy Wingo
2013-04-01 20:03 ` Mark H Weaver
2013-04-01 20:54 ` Andy Wingo
2013-04-01 21:04 ` Andy Wingo
2013-03-31 19:44 ` [PATCH] Add private port structure, and " Mark H Weaver
2013-03-31 22:08 ` Ludovic Courtès
2013-04-01 19:04 ` Andy Wingo
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: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ip4cr3ir.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=wingo@pobox.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.
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).