unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@glug.org>
Cc: emacs-devel@gnu.org
Subject: Re: [vms] extending Lisp_Process
Date: 14 Jul 2003 17:19:02 -0400	[thread overview]
Message-ID: <jkhe5odcxl.fsf@glug.org> (raw)
In-Reply-To: "Stefan Monnier"'s message of "Mon, 14 Jul 2003 09:37:45 -0400"

"Stefan Monnier" <monnier+gnu/emacs@cs.yale.edu> writes:

   I don't see a problem with it, other than the fact that you won't want
   to include it at the very beginning since the GC assumes that the
   structure starts with a `size' and a `next' field like all other
   vectors and VectorLike structs.

good thing to keep in mind.  thanks for the tip.

thi

  reply	other threads:[~2003-07-14 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 10:15 [vms] extending Lisp_Process Thien-Thi Nguyen
2003-07-14 13:37 ` Stefan Monnier
2003-07-14 21:19   ` Thien-Thi Nguyen [this message]
2003-07-14 15:50 ` Richard Stallman

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=jkhe5odcxl.fsf@glug.org \
    --to=ttn@glug.org \
    --cc=emacs-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.
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).