From: Andreas Roehler <andreas.roehler@easy-emacs.de>
Cc: Richard Stallman <rms@gnu.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: general-purpose.el - a general-forms-resource-utility
Date: Fri, 07 Jul 2006 10:50:25 +0200 [thread overview]
Message-ID: <44AE2051.6080308@easy-emacs.de> (raw)
In-Reply-To: <jkac7l6e8p.fsf@glug.org>
Thien-Thi Nguyen schrieb:
> Andreas Roehler <andreas.roehler@easy-emacs.de> writes:
>
>
>> Why not think about a way to relate and reflect these different
>> - already exiting and delivered - definitions?
>>
>
> probably this has already been thought about. see, for example:
>
> http://www.norvig.com/paip/unify.lisp
> http://www.norvig.com/paip/README.html
>
> a related idea is to unify byte-code -- that would be cool.
>
> thi
>
Thanks a lot! That's real interesting stuff there.
Let me say nonetheless that `unification' might be a
result--and certainly will be in some cases--but not
the primary goal of the project - that's wider, a more
general one.
If we agree that scattered general-purpose-functions
exist, one of the interesting questions is: Why?
What is the situation of the developer while writing
the fourth or fifth string-strip function?
Might be that
- none of the existing are suitable
- he ignores the other one.
Both seems possible, also in combination.
As big as the sources are I doubt that someone will
claim to know everything.
Also the question of suitability is no easy one -
following the discussion around string-strip these days
I don't see a way of automatized unification.
In any case it would help a lot if we could - while
writing - give some keyword, for example `correct user
input' and get a list of possible forms.
(That's the case already with `apropos' somehow, that's
not a new idea as such, so I will also examine
`apropos' in this context.)
__
Andreas Roehler
next prev parent reply other threads:[~2006-07-07 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 10:11 general-purpose.el - a general-forms-resource-utility Andreas Roehler
2006-07-06 19:57 ` Eli Zaretskii
2006-07-06 20:34 ` Lennart Borgman
2006-07-07 6:13 ` Andreas Roehler
2006-07-07 4:14 ` Richard Stallman
2006-07-07 6:32 ` Andreas Roehler
2006-07-07 7:55 ` Thien-Thi Nguyen
2006-07-07 8:50 ` Andreas Roehler [this message]
2006-07-07 16:04 ` Thien-Thi Nguyen
2006-07-08 1:12 ` Richard Stallman
2006-07-07 4:15 ` Richard Stallman
2006-07-07 7:08 ` Andreas Roehler
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=44AE2051.6080308@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=emacs-devel@gnu.org \
--cc=rms@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).