From: "Neil Jerram" <neiljerram@googlemail.com>
To: mikael@djurfeldt.com
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: [PATCH] Avoid `SCM_VALIDATE_LIST ()'
Date: Sun, 7 Sep 2008 15:32:34 +0200 [thread overview]
Message-ID: <49dd78620809070632n5bf63dcfgc27c681b2e7a0eb0@mail.gmail.com> (raw)
In-Reply-To: <66e540fe0809061611m12f14e8lea685871c7f1e8cd@mail.gmail.com>
2008/9/7 Mikael Djurfeldt <mikael@djurfeldt.com>:
>
> >From my experience, there was a huge improvement in scheme program
> development time when we moved to real type-checking of lists from the
> kind of type-checking you seem to want to re-introduce. It's much
> easier to debug code if you can assume that hangs are not due to
> circular data structures.
Thanks for that data point!
> Having been part of Guile development for some time, it's sad to see
> how much work is put into changing code back and forth due to
> vacillating development goals.
(Oh dear, this seems to be my week for arguing with everybody... :-))
It is? I am not aware of any other recent changes that fall into this
category, are you?
(It is precisely because this change is unique, IMO, in churning code
for no benefit, so I am getting so heavy about it! :-))
> It's apparent how important it is to
> have a written development policy with design decisions and
> motivations.
Apart from the VM work, there has been little development recently
that is big enough to merit or need an upfront design. I would say we
have been mostly focussed for the last year on stability and
cross-platform support.
> Probably a lot of that should also be put directly into
> the code in the form of comments.
Agreed there! The Guile code could use a lot more comments.
Neil
next prev parent reply other threads:[~2008-09-07 13:32 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-31 22:02 [PATCH] Avoid `SCM_VALIDATE_LIST ()' Ludovic Courtès
2008-09-01 0:12 ` Han-Wen Nienhuys
2008-09-01 20:19 ` Neil Jerram
2008-09-01 20:30 ` Ludovic Courtès
2008-09-02 2:40 ` Han-Wen Nienhuys
2008-09-06 22:23 ` Neil Jerram
2008-09-06 21:36 ` Neil Jerram
2008-09-07 4:23 ` Ken Raeburn
2008-09-07 15:24 ` Neil Jerram
2008-09-07 17:30 ` Ken Raeburn
2008-09-07 19:21 ` Neil Jerram
2008-09-08 23:11 ` Neil Jerram
2008-09-09 8:28 ` Ludovic Courtès
2008-09-10 20:43 ` Neil Jerram
2008-09-04 18:24 ` Andy Wingo
2008-09-05 0:10 ` Han-Wen Nienhuys
2008-09-05 1:06 ` Andy Wingo
2008-09-06 22:45 ` Neil Jerram
2008-09-07 2:33 ` Han-Wen Nienhuys
2008-09-07 13:38 ` Neil Jerram
2008-09-07 15:00 ` Han-Wen Nienhuys
2008-09-07 16:19 ` Neil Jerram
2008-09-07 19:25 ` Han-Wen Nienhuys
2008-09-07 14:05 ` Andy Wingo
2008-09-07 15:38 ` development goals (was: [PATCH] Avoid `SCM_VALIDATE_LIST ()') Han-Wen Nienhuys
2008-09-07 20:03 ` Neil Jerram
2008-09-08 4:28 ` development goals Han-Wen Nienhuys
2008-09-08 10:16 ` Ludovic Courtès
2008-09-08 13:57 ` Han-Wen Nienhuys
2008-09-09 7:08 ` Andy Wingo
2008-09-08 10:27 ` Ludovic Courtès
2008-09-06 22:40 ` [PATCH] Avoid `SCM_VALIDATE_LIST ()' Neil Jerram
2008-09-01 21:09 ` Neil Jerram
2008-09-01 21:47 ` Ludovic Courtès
2008-09-06 22:15 ` Neil Jerram
2008-09-08 9:40 ` Ludovic Courtès
2008-09-06 23:11 ` Mikael Djurfeldt
2008-09-07 2:43 ` Han-Wen Nienhuys
2008-09-07 15:04 ` Neil Jerram
2008-09-07 13:32 ` Neil Jerram [this message]
2008-09-02 2:44 ` Han-Wen Nienhuys
2008-09-06 22:32 ` Neil Jerram
2008-09-08 3:13 ` Han-Wen Nienhuys
2008-09-08 4:42 ` Clinton Ebadi
2008-09-08 9:47 ` Ludovic Courtès
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=49dd78620809070632n5bf63dcfgc27c681b2e7a0eb0@mail.gmail.com \
--to=neiljerram@googlemail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mikael@djurfeldt.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.
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).