emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien Guerry <bzg@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Add ob-sclang.el for sclang Org-mode babel support in contrib/
Date: Mon, 19 Jun 2017 12:37:43 +0200	[thread overview]
Message-ID: <87o9tkxnyg.fsf@bzg.fr> (raw)
In-Reply-To: <87y3sobagb.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 19 Jun 2017 11:20:20 +0200")

Hi Nicolas,

I'm all for lexical-binding, and it's good to have it in Org's core.

The author of ob-sclang.el used "2011-2017" for the copyright years,
which was obviously a typo and tells that the header was simply copied
from another file (which is 100% fine btw).

From that, I inferred that the "lexical-binding:t" was also copied
without further thinking, especially since there is no binding at all
in this file.

I think Stardiviner is the one who should make the decision, but I
don't see what "lexical-binding:t" would add to his actual code.

For the more general concern: again, I'm all for lexical binding and
I'm well aware of its numerous advantages, but I don't think we should
rule dynamic binding from contributed Org code.  Dynamic binding has
it's limitations, but when used carefully, it also has the advantage
of being easier to grok for beginners.  We want to welcome beginner's
contributions.  So I simply recommand lexical binding for Org's core,
and what fits developers best for Org's contributions.

And I agree we can move on to something else :)

-- 
 Bastien

  parent reply	other threads:[~2017-06-19 10: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
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 [this message]
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=87o9tkxnyg.fsf@bzg.fr \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).