From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: What does "lacks a prefix" mean?
Date: Sun, 12 Jul 2015 03:47:07 +0200 [thread overview]
Message-ID: <87d1zydu5g.fsf@nl106-137-147.student.uu.se> (raw)
In-Reply-To: 082e0be8-425b-4eff-8473-0c1091628695@default
Drew Adams <drew.adams@oracle.com> writes:
> Harm? Why would *harm* be the only useful or the
> most useful criterion?
>
> There's no harm in writing Lisp with no whitespace
> at all, except for that needed to distinguish tokens
> such as symbols and numbers.
>
> And in fact I once had a colleague (an expert Lisper,
> BTW) who wrote Lisp that way, always - no newline
> chars, no indentation, no spaces or tabs at all,
> except what was needed by the interpreter or
> byte-compiler to disambiguate the code.
>
> No one else wanted to read, let alone modify his
> code, but hey, no "harm" done, right?
>
> He wrote his code at lightning speed, hardly looking
> at it. And his code was *good* code - for the
> applications and the machine. It just wasn't very
> good for humans (other than himself, arguably, and
> I'm not sure he didn't shoot himself in the foot
> sometimes).
I do see the harm in doing as your former colleague but
I don't see the harm in using `let*' instead of `let'.
Apart from convention which can be reprogrammed in the
minds of programmers, even. And, as it stands, apart
from me not liking the syntax (spelling) of "let*"
compared to "let".
> I would say this about using `let' vs `let*' wrt
> what they indicate to human readers: `let' indicates
> that the bindings are independent; `let*' signals
> that they might be dependent.
>
> I don't see a red flag from `let*', but yes, it does
> make me pay attention and look for dependencies.
> That "might be" is where I agree with Barry: `let*'
> makes you look for whether each binding after the
> first might in fact be dependent on a previous one
> from the same `let*'.
>
> It's a huge load off one's mind knowing that the
> bindings of a `let' are independent. Similarly, it
> is a great help to know, from `let*', to look for
> how the bindings are actually related.
>
> The problem with using `let*' all the time ("harm",
> actually) is the problem of affixing the same
> **WARNING** label to absolutely everything - it
> loses all power to draw attention to anything.
> If everwhere might involve binding dependencies then
> you have no signal to watch for them. You need to
> always be on the alert - or never.
This all makes sense if the premise is that
dependencies are anything to look for, be aware of, be
"on the alert", as you say.
But - why do you want to look for them at all?
What does it matter? On the contrary, I consider them
completely natural and a good thing. It is *good* for
humans to see that computation is done in steps, and
for machines, that is the way it happens anyway - it
doesn't matter if you have one all but neverending
line:
(let ((value (computation_1 ( ... (computation_n ...))))))
or the same procedure on a vertical line with names to
illustrate the process. But, to humans, it is more
clear and less error prone, and it is easier to
modify and debug.
If we turn the discussion upside down, if dependencies
indeed were a reason to be on the alert - then I'd
like a much better and more specific construct than
`let*'! If dependencies were something to look for,
I wouldn't want a construct that says "here, there
*might* be dependencies", instead I'd like a construct
that said "here, there *is* a dependency, namely
X depends on Y in terms of Z!"
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2015-07-12 1:47 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 16:32 What does "lacks a prefix" mean? BobD
2015-07-08 16:45 ` Barry Margolin
2015-07-08 16:59 ` Vaidheeswaran C
2015-07-08 17:10 ` Vaidheeswaran C
2015-07-08 18:17 ` BobD
2015-07-08 18:21 ` Pascal J. Bourguignon
2015-07-08 18:45 ` BobD
2015-07-08 23:24 ` Emanuel Berg
2015-07-09 15:23 ` Filipp Gunbin
2015-07-09 22:32 ` Emanuel Berg
2015-07-10 17:04 ` Stefan Monnier
2015-07-11 22:42 ` Emanuel Berg
[not found] ` <mailman.6748.1436654668.904.help-gnu-emacs@gnu.org>
2015-07-11 23:58 ` Barry Margolin
2015-07-13 12:26 ` Filipp Gunbin
[not found] ` <mailman.6685.1436547891.904.help-gnu-emacs@gnu.org>
2015-07-10 18:27 ` Barry Margolin
[not found] ` <mailman.6612.1436455429.904.help-gnu-emacs@gnu.org>
2015-07-09 23:27 ` Barry Margolin
[not found] ` <mailman.6643.1436488423.904.help-gnu-emacs@gnu.org>
2015-07-10 0:49 ` Pascal J. Bourguignon
2015-07-10 5:04 ` Drew Adams
2015-07-10 14:42 ` Barry Margolin
[not found] ` <<barmar-2BC802.10421910072015@88-209-239-213.giganet.hu>
2015-07-10 14:53 ` Drew Adams
[not found] ` <<barmar-500871.19271109072015@88-209-239-213.giganet.hu>
2015-07-10 0:33 ` Drew Adams
[not found] ` <mailman.6590.1436397914.904.help-gnu-emacs@gnu.org>
2015-07-09 14:01 ` Barry Margolin
2015-07-09 14:10 ` Rusi
2015-07-09 22:27 ` Emanuel Berg
[not found] ` <mailman.6639.1436481016.904.help-gnu-emacs@gnu.org>
2015-07-10 3:10 ` Rusi
2015-07-10 16:00 ` Emanuel Berg
2015-07-09 22:19 ` Emanuel Berg
[not found] ` <<barmar-F23189.10014209072015@88-209-239-213.giganet.hu>
2015-07-09 15:33 ` Drew Adams
2015-07-12 1:47 ` Emanuel Berg [this message]
2015-07-12 16:59 ` Drew Adams
2015-07-13 0:46 ` Emanuel Berg
2015-07-13 7:26 ` Yuri Khan
2015-07-13 23:47 ` Emanuel Berg
2015-07-14 6:23 ` Yuri Khan
2015-07-14 21:58 ` Emanuel Berg
2015-07-19 0:59 ` Robert Thorpe
2015-07-28 0:24 ` Emanuel Berg
2015-07-30 1:40 ` Robert Thorpe
[not found] ` <mailman.7638.1438220428.904.help-gnu-emacs@gnu.org>
2015-07-30 2:49 ` Rusi
2015-07-30 2:53 ` Rusi
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=87d1zydu5g.fsf@nl106-137-147.student.uu.se \
--to=embe8573@student.uu.se \
--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.