unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Julian Graham <joolean@gmail.com>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel <guile-devel@gnu.org>
Subject: Re: NEWS entries -- user-visible?
Date: Sun, 14 Jun 2009 23:41:06 +0100	[thread overview]
Message-ID: <87bpoq8mm5.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <2bc5f8210906141243l630335e0o3fb771f22e94a962@mail.gmail.com> (Julian Graham's message of "Sun\, 14 Jun 2009 15\:43\:24 -0400")

Julian Graham <joolean@gmail.com> writes:

> Hi Andy,
>
> As mentioned on IRC, I bet there are ways to pitch these changes to
> make them comprehensible to users.  I think you're right to ditch the
> second one, but for the first and third:
>
>>    ** Guile now uses Gnulib as a portability aid
>
> ** Guile now uses components from Gnulib for portability to a wider
> variety of POSIX and non-POSIX systems.

I see where you're heading with this, but for me this NEWS item still
isn't specific enough to mean anything to a user.

It seems we're aiming towards saying:

** Guile now runs correctly on more platforms.  Since the 1.8.x
   series, support for the following platforms has been added: A, B,
   C.

But (1) I'm not sure we have precise information to hand on what A, B
and C are; and there's no value in the NEWS item without the detail.

And (2) to be honest there is no such thing as "runs correctly".  What
we really mean is that we've fixed particular portability-related bugs
on particular platforms by using Gnulib.  And we really ought to have
- and in most cases I think we already do have - specific NEWS items
for each of those bugs.

So, overall, I'm not persuaded that there's any value in this item.

>>    ** Primitive procedures with more than 3 arguments (aka. "gsubrs") are
>>    no longer implemented using the "compiled closure" mechanism.  This
>>    simplifies code and reduces both the storage and run-time overhead.
>
> ** Primitive procedures accepting more than 3 arguments now execute
> faster and consume less memory.

Here, on the other hand, I now agree with you; this is likely to be
interest to application developers.  It would be even better if it had
a pointer to where to find more details - even a mailing list thread
or a commit, if there's nothing better?

Regards,
        Neil




  reply	other threads:[~2009-06-14 22:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 18:32 NEWS entries -- user-visible? Andy Wingo
2009-06-14 19:43 ` Julian Graham
2009-06-14 22:41   ` Neil Jerram [this message]
2009-06-18 20:48     ` Ludovic Courtès
2009-06-19 17:47       ` Neil Jerram
2009-06-19 17:58         ` Ludovic Courtès
2009-06-19 18:08           ` Neil Jerram
2009-06-19 18:13             ` Ludovic Courtès
2009-06-27 22:05               ` Neil Jerram
2009-06-27 23:14                 ` Ludovic Courtès
2009-06-29 19:19                   ` Neil Jerram
2009-06-29 21:01                     ` Ludovic Courtès
2009-06-14 20:39 ` Neil Jerram
2009-06-18 20:49 ` 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=87bpoq8mm5.fsf@arudy.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=joolean@gmail.com \
    --cc=wingo@pobox.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).