unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r117987: * internals.texi (Stack-allocated	Objects): Describe this feature.
Date: Tue, 30 Sep 2014 21:49:55 +0200	[thread overview]
Message-ID: <87wq8kj3bw.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 83y4t0kiu4.fsf@gnu.org

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Tue, 30 Sep 2014 12:15:34 -0700
>> From: Paul Eggert <eggert@cs.ucla.edu>
>> 
>> Regardless of whether we use declaration-style macros, there is one 
>> thing I'd like to change: the macro names.
>
> Yes, the names are not helpful.
>
>> These macros are not about *scope*; they are about *lifetime*.  How
>> about the prefix "auto_" (from the C keyword 'auto') rather than
>> "scope_"?  Or maybe "block_" because it's block lifetime?  ("auto_"
>> is shorter....)
>
> Or maybe "alloca_*", as in alloca_string, alloca_list1, etc.

alloca is "to end of function".  Language-supported dynamic allocations
are "to end of block".  That's not quite the same.

-- 
David Kastrup




  reply	other threads:[~2014-09-30 19:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1XYzSf-00075J-Dr@vcs.savannah.gnu.org>
2014-09-30 17:55 ` [Emacs-diffs] trunk r117987: * internals.texi (Stack-allocated Objects): Describe this feature Stefan Monnier
2014-09-30 19:15   ` Paul Eggert
2014-09-30 19:29     ` Eli Zaretskii
2014-09-30 19:49       ` David Kastrup [this message]
2014-09-30 20:20     ` Stefan Monnier
2014-10-01  3:31       ` Paul Eggert

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=87wq8kj3bw.fsf@fencepost.gnu.org \
    --to=dak@gnu.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).