From: <tomas@tuxteam.de>
To: emacs-devel@gnu.org
Subject: Re: Changing line widths in the Emacs source code
Date: Mon, 14 Sep 2020 09:42:30 +0200 [thread overview]
Message-ID: <20200914074230.GA13929@tuxteam.de> (raw)
In-Reply-To: <p915z8hdrd7.fsf@google.com>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
On Sun, Sep 13, 2020 at 07:28:04PM -0700, T.V Raman wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> This could also be language specific. Languages like Java and perhaps
> also C++ end up with unduely long identifiers when you have a complex
> package/module system in use --- that then makes 80 columns hard.
In the foreword to SICP [1], Alan Perlis writes
"Algol 60, [...] lives inthe genes of Scheme and Pascal.
[...]
Pascal is for building pyramids -- imposing, breathtaking,
static structures built by armies pushing heavy blocks
into place. Lisp is for building organisms -- imposing,
breathtaking, dynamic structures built by squads fitting
fluctuating myriads of simpler organisms into place."
There was no Java or C++ around back then, but I think they fit
the "Pascal" pattern even better than Pascal itself.
Pyramids are built, remember, of huge stone blocks.
Cheers
[1] https://mitpress.mit.edu/sites/default/files/sicp/full-text/book/book-Z-H-5.html#%_chap_Temp_2
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2020-09-14 7:42 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-13 13:45 Changing line widths in the Emacs source code Lars Ingebrigtsen
2020-09-13 13:58 ` Stefan Kangas
2020-09-13 14:09 ` Lars Ingebrigtsen
2020-09-13 15:53 ` Stefan Kangas
2020-09-13 16:21 ` Lars Ingebrigtsen
2020-09-13 16:51 ` Yuan Fu
2020-09-13 16:58 ` Lars Ingebrigtsen
2020-09-13 17:55 ` Stephen Leake
2020-09-13 18:04 ` arthur miller
2020-09-13 17:34 ` Eric Abrahamsen
2020-09-13 17:54 ` Stephen Leake
2020-09-13 14:22 ` Alan Mackenzie
2020-09-13 18:38 ` Vladimir Sedach
2020-09-13 20:13 ` Göktuğ Kayaalp
2020-09-13 20:52 ` Stefan Monnier
2020-09-13 21:23 ` Göktuğ Kayaalp
2020-09-14 0:08 ` Tim Cross
2020-09-13 23:45 ` Óscar Fuentes
2020-09-14 2:23 ` Stefan Monnier
2020-09-14 2:28 ` T.V Raman
2020-09-14 7:42 ` tomas [this message]
2020-09-14 9:59 ` Alan Third
2020-09-15 7:25 ` Stefan Kangas
2020-09-13 14:53 ` Daniel Martín
2020-09-13 15:01 ` Lars Ingebrigtsen
2020-09-13 17:23 ` Andy Moreton
2020-09-13 17:29 ` Lars Ingebrigtsen
2020-09-13 18:07 ` Göktuğ Kayaalp
2020-09-13 15:09 ` Stefan Kangas
2020-09-13 14:54 ` Eli Zaretskii
2020-09-13 14:57 ` Lars Ingebrigtsen
2020-09-13 15:13 ` Eli Zaretskii
2020-09-13 17:15 ` Lars Ingebrigtsen
2020-09-13 15:27 ` Stefan Monnier
2020-09-13 17:31 ` Dmitry Gutov
2020-09-13 17:34 ` Andrea Corallo via Emacs development discussions.
2020-09-16 6:42 ` jeremyb
2020-09-13 15:28 ` Göktuğ Kayaalp
2020-09-13 15:43 ` Óscar Fuentes
2020-09-13 17:07 ` Amin Bandali
2020-09-13 18:01 ` Stephen Leake
2020-09-13 18:17 ` Göktuğ Kayaalp
2020-09-14 3:50 ` Richard Stallman
2020-09-14 19:25 ` David Koppelman
2020-09-15 8:53 ` Lars Brinkhoff
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=20200914074230.GA13929@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=emacs-devel@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.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).