From: Neil Jerram <neil@ossau.uklinux.net>
To: "Marco Maggi" <marco.maggi-ipsu@poste.it>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: the future of Guile
Date: Tue, 04 Dec 2007 23:00:00 +0000 [thread overview]
Message-ID: <87fxyioykv.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <JSIJ0R$54F55A518E52A4B6C8A09A3378AEEDDD@poste.it> (Marco Maggi's message of "Tue, 4 Dec 2007 07:50:51 +0100")
"Marco Maggi" <marco.maggi-ipsu@poste.it> writes:
> 3. For Guile 2.0 backwards compatibility at the C level can
> be broken. Freely. No shame. No blame.
Disagree, in general. Why should we be arbitrarily awkward? If there
are specific motivations, we should consider those case by case.
> 2. GOOPS always there.
I think I agree. I haven't developed Ludovic's suspicions yet.
> 3b. Death to structs! IMO they were "an attempt", but the
> resulting code is awful (sorry, but can you disagree?).
Err.. but aren't structs the main part of how GOOPS is implemented?
> 6. More modularity.
Yes, definitely, in general. Like others I don't agree with trying to
split up the numerical tower though.
> 8. Hackability of the core. If nobody understands it...
Is it really that difficult?
(Actually the array code is pretty nasty, that could do with cleanup
if we can do that without breaking it!)
> 8c. This is for my own ego: yeah, yeah, yeah! Define:
>
> typedef SCM scm_t;
>
> Emacs font locking kisses "scm_t" automatically.
Surely there's an elisp incantation that would make it kiss SCM for
you?
> 1. TCL has nice programs that allow to distribute single
> file auto-extracting-and-running archives holding the
> core executable, shared libraries, pure TCL modules and
> some data files (search for "tclkit").
I don't think that a programming language should have its own
packaging system. Instead, we should provide tools to make it trivial
to package up Guile code into the common kinds of distribution
package.
> 3. Resurrect SCWM (Scheme Constraints Window Manager).
I've settled happily on ion2 now. I suspect a WM may be one of those
things that doesn't really need much scripting, so I'm not sure what
SCWM would be aiming at.
Regards,
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2007-12-04 23:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 6:50 the future of Guile Marco Maggi
2007-12-04 8:48 ` Stephen Compall
2007-12-04 12:41 ` Ludovic Courtès
2007-12-04 14:50 ` Bill Schottstaedt
2007-12-04 15:30 ` Ludovic Courtès
2007-12-04 23:00 ` Neil Jerram [this message]
2007-12-05 23:11 ` Andy Wingo
2007-12-06 19:48 ` Mikael Djurfeldt
[not found] <F8.1B.18780.B4965574@avas11>
2007-12-04 15:55 ` the future of guile Daniel Llorens del Río
[not found] <cmu-lmtpd-7104-1196779864-1@mail-imap2.uio.no>
2007-12-04 18:08 ` the future of Guile Kjetil S. Matheussen
2007-12-04 18:34 ` Kjetil S. Matheussen
2007-12-04 20:06 ` Roland Orre
2007-12-04 20:42 ` Ludovic Courtès
2007-12-04 22:30 ` Kjetil S. Matheussen
[not found] <34.F3.20110.D6985574@avas19>
2007-12-04 19:54 ` the future of guile Daniel Llorens del Río
-- strict thread matches above, loose matches on Subject: below --
2007-12-05 9:01 the future of Guile Marco Maggi
2007-12-05 14:19 ` Roland Orre
2007-12-05 20:28 ` Ludovic Courtès
2007-12-05 15:40 Mike Gran
2007-12-05 16:05 ` Julian Graham
2007-12-05 16:18 ` Daniel Ridge
2007-12-05 20:41 ` Ludovic Courtès
2007-12-05 21:02 Marco Maggi
2007-12-05 22:32 Marco Maggi
2007-12-05 22:56 ` Ludovic Courtès
[not found] <cmu-lmtpd-27643-1196871540-1@mail-imap2.uio.no>
2007-12-06 14:52 ` Kjetil S. Matheussen
2007-12-07 6:28 Marco Maggi
[not found] <cmu-lmtpd-4316-1197047238-3@mail-imap2.uio.no>
2007-12-07 17:42 ` Kjetil S. Matheussen
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fxyioykv.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-user@gnu.org \
--cc=marco.maggi-ipsu@poste.it \
/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.
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).