From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: char-ready? for soft ports
Date: 08 Oct 2002 22:58:21 +0200 [thread overview]
Message-ID: <87elb0wsuq.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m34rc3f90e.fsf@laruns.ossau.uklinux.net>
Neil Jerram <neil@ossau.uklinux.net> writes:
> Thoughts? Is there a reason I've missed why soft ports should not
> support char-ready? completely?
I can't think of any.
> Should I commit this?
Yes, please.
> (Is the use of SCM_INUM in sf_input_waiting safe?)
I don't think so. Using scm_uint2num or scm_int2num should not be a
significant overhead.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-10-08 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 22:33 char-ready? for soft ports Neil Jerram
2002-10-08 20:58 ` Marius Vollmer [this message]
2002-10-09 18:21 ` Neil Jerram
2002-10-09 19:23 ` Neil Jerram
2002-10-09 19:35 ` Marius Vollmer
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=87elb0wsuq.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@gnu.org \
/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).