unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Göran Weinholt" <INVALID.NOREPLY@gnu.org>
To: "Göran Weinholt" <goran@weinholt.se>, bug-guile@gnu.org
Subject: [bug #31681] string-filter argument order doesn't match SRFI-13
Date: Wed, 17 Nov 2010 13:15:31 +0000	[thread overview]
Message-ID: <20101117-141530.sv2373.84512@savannah.gnu.org> (raw)
In-Reply-To: 


URL:
  <http://savannah.gnu.org/bugs/?31681>

                 Summary: string-filter argument order doesn't match SRFI-13
                 Project: Guile
            Submitted by: weinholt
            Submitted on: Wed Nov 17 14:15:30 2010
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

This is the order of arguments given by SRFI-13:

 string-filter char/char-set/pred s [start end] -> string
 string-delete har/char-set/pred s [start end] -> string

This is the order used by Guile:

 -- Scheme Procedure: string-filter s char_pred [start [end]]
 -- Scheme Procedure: string-delete s char_pred [start [end]]

I think it would be good if the srfi-13 module used the standard argument
order.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?31681>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




             reply	other threads:[~2010-11-17 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 13:15 Göran Weinholt [this message]
2010-11-19 16:05 ` [bug #31681] string-filter argument order doesn't match SRFI-13 Andy Wingo

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=20101117-141530.sv2373.84512@savannah.gnu.org \
    --to=invalid.noreply@gnu.org \
    --cc=bug-guile@gnu.org \
    --cc=goran@weinholt.se \
    /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).