From: storm@cua.dk (Kim F. Storm)
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: QNX subprocess bug
Date: Wed, 05 Apr 2006 11:01:14 +0200 [thread overview]
Message-ID: <m3mzf0gzvp.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <878xqlhs8m.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 04 Apr 2006 18:55:34 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> I think the best solution is to keep pid_t values (without changing them
> into Lisp_Object values) as long as possible, and to use floats when turning
> them into Lisp_Object.
Thanks Stefan.
This is a change that I have wanted to make for a very long time!
However, I would change the following not-really-Lisp_Object fields as well:
unsigned pty_flag : 1;
== !NILP (pty_flag)
unsigned inherit_coding_system_flag : 1;
== !NILP (inherit_coding_system_flag)
unsigned read_output_skip : 1;
== !NILP (read_output_skip)
int read_output_delay;
== XINT (read_output_delay)
The adaptive_read_buffering field could be replaced by two new
fields (which would also improve code readability):
unsigned adaptive_read_buffering : 1;
== !NILP (Vprocess_adaptive_read_buffering);
unsigned adaptive_read_buffering_clear_on_write : 1;
== EQ (Vprocess_adaptive_read_buffering, Qt)
I also noticed that the field encoding_carryover is no longer used,
so it can be deleted.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2006-04-05 9:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 18:00 QNX subprocess bug bob
2006-04-04 22:55 ` Stefan Monnier
2006-04-05 3:47 ` Richard Stallman
2006-04-05 9:01 ` Kim F. Storm [this message]
2006-04-05 13:03 ` Stefan Monnier
2006-04-05 19:06 ` Richard Stallman
[not found] <gD4Vf.180176$B94.1009@pd7tw3no>
2006-03-26 0:22 ` Richard Stallman
2006-03-26 4:26 ` Eli Zaretskii
2006-03-27 8:35 ` Richard Stallman
2006-03-27 22:26 ` Kim F. Storm
2006-03-31 3:11 ` Richard Stallman
2006-03-26 4:33 ` Stefan Monnier
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3mzf0gzvp.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=rms@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).