all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Sharp--quote [was: url-retrieve fails on most HTTPS sites]
Date: Tue, 29 Sep 2020 16:14:21 +0200	[thread overview]
Message-ID: <20200929141421.GA13194@tuxteam.de> (raw)
In-Reply-To: <87blhoq2kb.fsf@ebih.ebihd>

[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]

On Tue, Sep 29, 2020 at 12:50:44PM +0200, Emanuel Berg via Users list for the GNU Emacs text editor wrote:
> tomas wrote:

[...]

> > Plus lots of other optimizations the compiler can
> > do if it knows that it's the function value you are
> > talking about.
> 
> Yeah, you have an example of this?

I think Stefan is in a far better position to answer
that.

One of the things is that, if the compiler knows you're
going for the function definition, it can warn you if
it "knows" this to be unbound in the relevant context.

It might also eliminate check code if it knows that
value to be present (or even use the value directly).

> BTW how does _Lisp_ know what is refered to? [...]

Syntactical context: if you say

  (foo 1 2 3)

it knows it has to look up things in the variable's function
cell, whereas in

  (+ 1 2 foo 3)

it goes and looks up foo's variable's value cell.

> > Plus the clarity of your code for your other readers.
> 
> It makes the code _cooler_ but more clear, I don't
> know, really. Perhaps to some.

As usually, it takes some familiarity. But if I see, in the
middle of something

  (mumble 1 2 #'foo 5)

...then I /know/ "aah, foo is being passed as a function".
Whereas if I see

  (mumble 1 2 'foo 5)

...then I just don't know. It might be used as a function,
as a symbol... whatever.

Cheers
 - t

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2020-09-29 14:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 20:41 url-retrieve fails on most HTTPS sites Nicolas Graner
2020-09-28 23:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-28 23:24   ` 2QdxY4RzWzUUiLuE
2020-09-28 23:41     ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29  2:26       ` Stefan Monnier
2020-09-29  3:24         ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29  9:31           ` tomas
2020-09-29  9:49             ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 10:32               ` tomas
2020-09-29 10:50                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 14:14                   ` tomas [this message]
2020-09-29 14:56                     ` Sharp--quote [was: url-retrieve fails on most HTTPS sites] Stefan Monnier
2020-09-29 15:19                       ` tomas
2020-09-29 16:03                         ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 16:01                       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29 15:18                     ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-29  3:45         ` url-retrieve fails on most HTTPS sites 황병희
2020-09-29  2:50       ` 2QdxY4RzWzUUiLuE
2020-09-29  5:45         ` Colin Baxter
2020-09-29 11:29           ` 2QdxY4RzWzUUiLuE
2020-09-29 13:57             ` Colin Baxter
2020-09-29 14:53         ` HTTPS fails (was: url-retrieve fails on most HTTPS sites) Nicolas Graner
2020-09-29 15:10           ` Nicolas Graner
2020-09-29 15:16           ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-09-29 14:47 ` url-retrieve fails on most HTTPS sites Noam Postavsky
2020-09-29 15:08   ` Nicolas Graner

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200929141421.GA13194@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.