From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Internal visibility
Date: Tue, 10 Jun 2008 10:04:14 +0200 [thread overview]
Message-ID: <87d4mpsold.fsf@ambire.localdomain> (raw)
In-Reply-To: <87iqwhn3jw.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 10 Jun 2008 09:37:39 +0200")
() ludo@gnu.org (Ludovic Courtès)
() Tue, 10 Jun 2008 09:37:39 +0200
Instead, applications should be written against an
encoding-oblivious API. This is what core R5RS constructs
and SRFI-1[34] provide at the Scheme level.
Unfortunately, that position doesn't provide a clean path
towards an encoding-knowledgable API. Better would be to design
an encoding-knowledgable API now (or as soon as possible), with
the encoding value `unencoded' (or `8-bit-raw' or what-have-you)
as default. This way, things are explicit and the (future)
changes to application code will be less invasive, or even
unnecessary.
In short, the current API is not actually "future proof" (yet).
Requiring obliviousness in the API makes for ugly work long term.
thi
next prev parent reply other threads:[~2008-06-10 8:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 23:46 [PATCH] Fix continuation problems on IA64 Neil Jerram
2008-05-08 20:09 ` Ludovic Courtès
2008-05-08 21:29 ` Neil Jerram
2008-05-09 8:15 ` Ludovic Courtès
2008-05-09 22:19 ` Neil Jerram
2008-05-11 3:06 ` Ludovic Courtès
2008-05-12 21:02 ` Neil Jerram
2008-05-14 3:45 ` Internal visibility Ludovic Courtès
2008-05-27 21:32 ` Ludovic Courtès
2008-05-31 21:23 ` Ludovic Courtès
2008-06-01 8:00 ` Neil Jerram
2008-06-01 11:05 ` Ludovic Courtès
2008-06-01 20:48 ` Neil Jerram
2008-06-01 22:02 ` Ludovic Courtès
2008-06-01 20:24 ` Han-Wen Nienhuys
2008-06-09 18:10 ` Neil Jerram
2008-06-10 1:51 ` Han-Wen Nienhuys
2008-06-10 7:37 ` Ludovic Courtès
2008-06-10 8:04 ` Thien-Thi Nguyen [this message]
2008-06-10 12:09 ` Ludovic Courtès
2008-06-11 7:49 ` Thien-Thi Nguyen
2008-06-11 12:20 ` Ludovic Courtès
2008-06-12 20:45 ` Mike Gran
2008-06-23 12:20 ` Ludovic Courtès
2008-06-11 4:05 ` Han-Wen Nienhuys
2008-06-11 7:18 ` Ludovic Courtès
2008-06-11 7:24 ` Clinton Ebadi
2008-06-11 7:39 ` Ludovic Courtès
2008-06-11 16:09 ` Han-Wen Nienhuys
2008-06-23 12:18 ` Ludovic Courtès
2008-06-11 7:37 ` Neil Jerram
2008-05-12 22:18 ` [PATCH] Fix continuation problems on IA64 Neil Jerram
2008-05-14 2:55 ` 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=87d4mpsold.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-devel@gnu.org \
--cc=ludo@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).