From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Sting abstraction 2
Date: Wed, 20 May 2009 23:11:36 +0200 [thread overview]
Message-ID: <878wkreayf.fsf@gnu.org> (raw)
In-Reply-To: 1242833049.32575.7271.camel@localhost.localdomain
Hello!
Mike Gran <spk121@yahoo.com> writes:
> Anyway, I backtracked a bit. Today I pushed a new tree
> (string_abstraction2) which should be the same as master except with all
> unnecessary calls to scm_i_string_chars, scm_i_symbol_chars, and
> scm_i_string_writable_chars removed. I largely avoided other
> unnecessary modifications. It is still an 8-bit string build, but, now
> the string internals have been confined to strings.c and strports.c,
> with very few exceptions.
How does it differ from the approach you took a while back (e.g.,
http://thread.gmane.org/gmane.lisp.guile.devel/8436)?
(The commit notification message is hard to follow because it contains
many commits in addition to the relevant ones.)
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-05-20 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 15:24 Sting abstraction 2 Mike Gran
2009-05-20 21:11 ` Ludovic Courtès [this message]
2009-05-20 22:49 ` Mike Gran
2009-05-20 23:32 ` Ludovic Courtès
2009-05-21 3:33 ` Mike Gran
2009-05-22 15:59 ` 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=878wkreayf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
/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).