unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Göran Weinholt" <INVALID.NOREPLY@gnu.org>
To: "Andy Wingo" <wingo@pobox.com>,
	"Göran Weinholt" <goran@weinholt.se>,
	"Mike Gran" <spk121@yahoo.com>,
	bug-guile@gnu.org
Subject: [bug #31680] R6RS string literal intraline whitespace removal
Date: Thu, 18 Nov 2010 19:45:17 +0000	[thread overview]
Message-ID: <20101118-204517.sv2373.2325@savannah.gnu.org> (raw)
In-Reply-To: <20101118-185600.sv20118.39996@savannah.gnu.org>


Follow-up Comment #3, bug #31680 (project guile):

I've used it for multiline strings, like so:

  (define modp-group1-p
    (string->number
     "FFFFFFFFFFFFFFFFC90FDAA22168C234C4C6628B80DC1CD1
      29024E088A67CC74020BBEA63B139B22514A08798E3404DD
      EF9519B3CD3A431B302B0A6DF25F14374FE1356D6D51C245
      E485B576625E7EC6F44C42E9A63A3620FFFFFFFFFFFFFFFF"
     16))

or like so:

        "My name is Ozymandias, king of kings:n
         Look on my works, ye Mighty, and despair!"

I think any implementation of multiline strings should be prepared to handle
characters from other operating systems. But surely you should not need to
check for U+205F and so on explictly, isn't it enough to see that they belong
to the right char-general-category?

    _______________________________________________________

Reply to this item at:

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

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




  reply	other threads:[~2010-11-18 19:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 12:15 [bug #31680] R6RS string literal intraline whitespace removal Göran Weinholt
2010-11-18 15:05 ` Mike Gran
2010-11-18 18:56   ` Andy Wingo
2010-11-18 19:45     ` Göran Weinholt [this message]
2010-11-18 20:24       ` Andy Wingo
2010-11-18 21:51         ` Mike Gran
2010-11-19 15:24           ` Andy Wingo
2010-11-19 17:57             ` Mike Gran
2011-01-21  7:35               ` Andy Wingo
2011-01-21  8:22                 ` 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=20101118-204517.sv2373.2325@savannah.gnu.org \
    --to=invalid.noreply@gnu.org \
    --cc=bug-guile@gnu.org \
    --cc=goran@weinholt.se \
    --cc=spk121@yahoo.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).