From: Philip Kaludercic <philipk@posteo.net>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Drew Adams <drew.adams@oracle.com>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Eli Zaretskii <eliz@gnu.org>, Eshel Yaron <me@eshelyaron.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [External] : Re: Question about eval and compile-command
Date: Fri, 04 Aug 2023 07:00:16 +0000 [thread overview]
Message-ID: <87fs4zl2bj.fsf@posteo.net> (raw)
In-Reply-To: <87cz038flv.fsf@linux-m68k.org> (Andreas Schwab's message of "Fri, 04 Aug 2023 08:51:40 +0200")
Andreas Schwab <schwab@linux-m68k.org> writes:
> On Aug 03 2023, Drew Adams wrote:
>
>>> > In retrospect, shouldn't the type be be a string or a function?
>>>
>>> Not a function, but a form.
>>
>> A string is a form too...
>
> But a function does not evaluate to a string.
I'll rephrase my comment to avoid confusion: "Instead of any accepting a
string, or any form (both of which are evaluated, which is not an issue
due to the fact that evaluation of strings is idempotent), it seems like
it would have been better if the expected type of `compile-command' were
either a string, that would be interpreted without any further
processing, or a function, that would be funcalled with the expectation
that it would return a string, which would be taken to be the compile
command."
prev parent reply other threads:[~2023-08-04 7:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 9:29 Question about eval and compile-command Eshel Yaron
2023-08-03 9:56 ` Eli Zaretskii
2023-08-03 15:14 ` Stefan Monnier
2023-08-03 16:23 ` Eshel Yaron
2023-08-03 17:24 ` Stefan Monnier
2023-08-03 20:02 ` Philip Kaludercic
2023-08-03 20:39 ` Stefan Monnier
2023-08-03 21:14 ` Andreas Schwab
2023-08-03 21:35 ` [External] : " Drew Adams
2023-08-04 5:40 ` Eli Zaretskii
2023-08-04 6:51 ` Andreas Schwab
2023-08-04 7:00 ` Philip Kaludercic [this message]
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=87fs4zl2bj.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=me@eshelyaron.com \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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).