unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: Guile Devel <guile-devel@gnu.org>
Subject: Re: [Guile-commits] GNU Guile branch, string-abstraction, updated. feda5bd1c08d69628ec9fdb5577d5c894b70b6e8
Date: Mon, 27 Apr 2009 06:53:36 -0700	[thread overview]
Message-ID: <1240840416.3133.230.camel@localhost.localdomain> (raw)
In-Reply-To: <87mya2pl4n.fsf@inria.fr>

On Mon, 2009-04-27 at 10:16 +0200, Ludovic Courtès wrote:
> Hello,

> Is `read_token2 ()' temporary?  (I didn't see it mentioned in the log.)
> 
> Otherwise I'd vote for a more descriptive name.
> 

It was meant to be temporary.

> >  static scm_t_uint32
> 
> BTW, I'm wondering whether we should have a separate type for wide
> chars, to make the intent clearer (say, `scm_t_char').
> 

OK

> > -    (pass-if "\\x08 backspace"
> > +    (pass-if "\\x08; backspace"
> >        (let ((port (open-output-string)))
> > -	(display "\x08" port)
> > +	(display "\x08;" port)

> We're introducing subtle incompatibilities here, which we'd rather
> avoid, by default at least.  Could you make that a reader option?

I'm getting there.  I pulled this idea of hex escapes out of the R6RS,
but, as a standard, I think it is a poor design.  Part of the reason for
moving hex escapes into their own function in the last push was to try
to centralize them, so that the reader option was possible.  

> 
> Likewise, I think we should avoid gratuitously changing exception
> messages since, unfortunately, they are sort-of part of the API.
> 

I can roll it back if you like.  I only changed it because of this line
in the Gnu coding standards.

"Please do not use the term 'illegal' to refer to erroneous input to a
computer program.  Please use 'invalid' for this, and reserve the term
'illegal' for activities prohibited by law."

> > --- a/test-suite/tests/regexp.test
> > +++ b/test-suite/tests/regexp.test
> > @@ -22,6 +22,8 @@
> >    #:use-module (test-suite lib)
> >    #:use-module (ice-9 regex))
> >  
> > +(setlocale LC_ALL "en_US.iso88591")
> 
> The user doesn't necessarily have this locale.  Can you instead use
> something similar to `under-french-locale-or-unresolved' in `i18n.test'
> or `find-latin1-locale' in `srfi-14.test', perhaps moving it to the
> `(test-suite lib)' module?

If that line ends up remaining more permanent, I will.  

-Mike Gran





      reply	other threads:[~2009-04-27 13:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Ly70v-000271-Au@cvs.savannah.gnu.org>
2009-04-27  8:16 ` [Guile-commits] GNU Guile branch, string-abstraction, updated. feda5bd1c08d69628ec9fdb5577d5c894b70b6e8 Ludovic Courtès
2009-04-27 13:53   ` Mike Gran [this message]

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=1240840416.3133.230.camel@localhost.localdomain \
    --to=spk121@yahoo.com \
    --cc=guile-devel@gnu.org \
    --cc=ludovic.courtes@inria.fr \
    /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).