From: Nic Ferrier <nferrier@ferrier.me.uk>
To: Bastien <bzg@gnu.org>
Cc: tromey@redhat.com, rms@gnu.org, drew.adams@oracle.com,
emacs-devel@gnu.org
Subject: Re: CommonLisp namespace system (was Re: adding namespaces to emacs-lisp (better elisp?))
Date: Sat, 27 Jul 2013 17:56:33 +0100 [thread overview]
Message-ID: <871u6k0wn2.fsf@ferrier.me.uk> (raw)
In-Reply-To: <87k3kcusa3.fsf@engster.org> (David Engster's message of "Sat, 27 Jul 2013 14:00:20 +0200")
David Engster <deng@randomsample.de> writes:
> Bastien writes:
>> You can have namespaces clashes too, it's purely conventional.
>>
>> So to me the only complaint is about symbols' length.
>>
>> But is that really such a big problem?
>>
>> The common practice for Emacs Lisp seems to favor explicit and long
>> names over terse and hard-to-decipher ones. I guess the length of
>> the symbols is more due to this (good) practice than to the length
>> of prefixes.
>
> For me, the main problem with the length of symbols is that I
> intuitively tend to avoid writing them. For instance, I usually avoid
> using defstructs for nicely wrapping global state, because always
> writing things like
>
> (setf (my-prefix-struct-somevalue my-prefix--struct) 'foobar)
>
> is just verbose and tiresome.
This is half the reason I want to do something about namespaces. When
names get very long indeed even the spaces start to disappear.
next prev parent reply other threads:[~2013-07-27 16:56 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 14:08 adding namespaces to emacs-lisp (better elisp?) Nic Ferrier
2013-07-26 14:34 ` Drew Adams
2013-07-26 17:01 ` Pascal J. Bourguignon
2013-07-26 17:01 ` CommonLisp namespace system (was Re: adding namespaces to emacs-lisp (better elisp?)) Nic Ferrier
2013-07-26 17:19 ` Drew Adams
2013-07-26 18:26 ` Sebastian Wiesner
2013-07-26 18:53 ` Drew Adams
2013-07-26 21:08 ` Pascal J. Bourguignon
2013-07-26 18:23 ` Stefan Monnier
2013-07-26 18:32 ` Nic Ferrier
2013-07-26 18:45 ` Tom Tromey
2013-07-26 18:58 ` Drew Adams
2013-07-26 19:06 ` Nic Ferrier
2013-07-26 20:46 ` CommonLisp namespace system Lars Brinkhoff
2013-07-26 20:57 ` Drew Adams
2013-07-26 21:47 ` Nic Ferrier
2013-07-29 17:31 ` Lars Brinkhoff
2013-07-26 20:57 ` CommonLisp namespace system (was Re: adding namespaces to emacs-lisp (better elisp?)) Drew Adams
2013-07-27 7:17 ` Richard Stallman
2013-07-27 8:13 ` Nic Ferrier
2013-07-27 11:43 ` Bastien
2013-07-27 12:00 ` David Engster
2013-07-27 16:56 ` Nic Ferrier [this message]
2013-07-27 23:52 ` Richard Stallman
2013-07-28 7:22 ` Nic Ferrier
2013-07-28 8:18 ` Jambunathan K
2013-07-28 12:10 ` Richard Stallman
2013-07-28 13:48 ` Nic Ferrier
2013-07-29 10:12 ` Richard Stallman
2013-07-29 10:45 ` Nic Ferrier
2013-07-30 0:31 ` Richard Stallman
2013-07-27 9:37 ` CommonLisp namespace system Lars Brinkhoff
2013-07-26 19:42 ` CommonLisp namespace system (was Re: adding namespaces to emacs-lisp (better elisp?)) Drew Adams
2013-07-26 21:26 ` Juanma Barranquero
2013-07-26 21:06 ` Pascal J. Bourguignon
2013-07-26 21:44 ` Nic Ferrier
2013-07-27 7:16 ` adding namespaces to emacs-lisp (better elisp?) Richard Stallman
2013-07-26 15:43 ` Stefan Monnier
2013-07-26 16:56 ` Nic Ferrier
2013-07-26 18:18 ` Stefan Monnier
2013-07-26 19:00 ` Nic Ferrier
2013-07-26 20:59 ` Stefan Monnier
2013-07-26 21:43 ` Nic Ferrier
2013-07-26 21:59 ` Drew Adams
2013-07-26 22:21 ` Stefan Monnier
2013-07-26 22:33 ` Nic Ferrier
2013-07-27 0:51 ` Stefan Monnier
2013-07-27 8:27 ` Nic Ferrier
2013-07-27 14:12 ` Stefan Monnier
2013-07-27 16:17 ` Nic Ferrier
2013-07-27 17:28 ` Stefan Monnier
2013-07-27 10:35 ` Pascal J. Bourguignon
2013-07-26 22:00 ` Drew Adams
2013-07-27 0:49 ` Stefan Monnier
2013-07-27 1:13 ` Drew Adams
2013-07-27 7:02 ` Lars Brinkhoff
2013-07-27 10:33 ` Pascal J. Bourguignon
2013-07-31 6:48 ` Lars Brinkhoff
2013-07-27 10:31 ` Pascal J. Bourguignon
2013-07-27 14:14 ` Stefan Monnier
2013-07-27 16:43 ` Drew Adams
2013-07-26 17:21 ` Davis Herring
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=871u6k0wn2.fsf@ferrier.me.uk \
--to=nferrier@ferrier.me.uk \
--cc=bzg@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=tromey@redhat.com \
/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.