From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Bastien Guerry <bzg@gnu.org>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Add ob-sclang.el for sclang Org-mode babel support in contrib/
Date: Sun, 18 Jun 2017 22:37:25 +0200 [thread overview]
Message-ID: <87a855c9ru.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87wp89rsfe.fsf@bzg.fr> (Bastien Guerry's message of "Sun, 18 Jun 2017 21:45:25 +0200")
Bastien Guerry <bzg@gnu.org> writes:
> I agree it's good to have lexical scoping, but I don't consider Elisp
> to be lexical scopped -- I consider Elisp to let the user pick up the
> constraints he wants, with dynamic binding still being the default.
Not at all. Lexical binding is still the way to go. If you need dynamic
binding, use a global variable, e.g., a defvar, so at least this is
explicit.
> Maybe lexical binding will be the default behavior one day, but in the
> meantime, I would suggest to use "-*- lexical-binding:t ; -*-" only if
> lexical binding is actually used in the file.
This is really not a good idea. Firstly, if lexical-binding is nil, no
code can use it (obviously). You will not get a warning saying "Hey,
your code would really benefit from lexical binding", either. You really
don't want to ponder about it at every non-trivial change you make in
the file. Secondly, when active, the compiler can reason (a bit) about
the code and report more informative errors. The code is more readable,
and therefore easier to debug, too.
There is absolutely no drawback in using lexical binding. Since Emacs
24.1, it _is_ the default for Elisp: every Elisp file created activates
it, the other binding being for compatibility with older libraries.
Please, pretty please, don't suggest it is different.
Regards,
next prev parent reply other threads:[~2017-06-18 20:37 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 0:43 Add ob-sclang.el for sclang Org-mode babel support in contrib/ numbchild
2017-06-10 8:17 ` Nicolas Goaziou
2017-06-11 2:02 ` numbchild
2017-06-14 14:02 ` Nicolas Goaziou
2017-06-15 6:21 ` Bastien Guerry
2017-06-15 7:53 ` numbchild
2017-06-15 7:56 ` numbchild
2017-06-15 8:26 ` Bastien Guerry
2017-06-15 11:19 ` numbchild
2017-06-15 11:14 ` numbchild
2017-06-15 12:38 ` Bastien Guerry
2017-06-16 23:25 ` numbchild
2017-06-17 10:53 ` Bastien Guerry
2017-06-17 12:23 ` numbchild
2017-06-17 12:46 ` Bastien Guerry
2017-06-17 13:14 ` numbchild
2017-06-17 14:27 ` Nicolas Goaziou
2017-06-18 8:34 ` Bastien Guerry
2017-06-18 9:31 ` Nicolas Goaziou
2017-06-18 19:45 ` Bastien Guerry
2017-06-18 20:37 ` Nicolas Goaziou [this message]
2017-06-18 21:32 ` Bastien Guerry
2017-06-19 9:20 ` Nicolas Goaziou
2017-06-19 10:14 ` Kaushal Modi
2017-06-19 10:37 ` Bastien Guerry
2017-06-19 14:44 ` numbchild
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a855c9ru.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@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/org-mode.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).