From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: guile-user@gnu.org, mckelvey@users.sourceforge.net
Subject: Re: SCM_LENGTH ???
Date: Tue, 11 Jan 2005 19:08:41 +0100 [thread overview]
Message-ID: <lju0pnx2hi.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <200501101003.10523.bkorb@veritas.com> (Bruce Korb's message of "Mon, 10 Jan 2005 10:03:10 -0800")
Bruce Korb <bkorb@veritas.com> writes:
> On Monday 10 January 2005 09:26 am, Marius Vollmer wrote:
>
>> The recommended way to check for deprecated features is to compile a
>> version of Guile with --disable-deprecated and compile/link/test
>> against that.
>
> That's a cute idea. I like it! I confess, I don't remember it from the last
> time I went through the Guile docs. When was that? '99 or '98?
> Have the docs changed much since then? ;-)
Yes!
>> [...]
> However, it is a bit premature to use scm_c_*_length functions since
> 1.7.x is a test release series and 1.8 is not available.
Yes, you are right. The recommended way in 1.6 is to use
SCM_STRING_LENGTH, for example. It _is_ annoying to have to switch
away from SCM_STRING_LENGTH in 1.8 again, I have to agree to that.
(The reason for this is that 1.8 wants you to move away from making
assumptions about the internals of strings so that we can switch more
easily to Unicode later.)
> To me, this still feels like grubbing around in internals and I do wish
> you all were willing to supply something that approximates it.
> I loathe having this in my code:
Ugh, the ports API is still this ugly...
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-01-11 18:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CmxC0-0003DB-Gx@sc8-sf-web1.sourceforge.net>
2005-01-07 17:31 ` SCM_LENGTH ??? Bruce Korb
2005-01-07 18:07 ` Marius Vollmer
2005-01-07 18:27 ` Bruce Korb
2005-01-10 17:26 ` Marius Vollmer
2005-01-10 18:03 ` Bruce Korb
2005-01-10 20:59 ` Greg Troxel
2005-01-11 18:08 ` Marius Vollmer [this message]
2005-01-11 23:40 ` Kevin Ryde
2005-01-12 10:33 ` Marius Vollmer
2005-01-10 20:34 ` Ken Raeburn
2005-01-11 16:12 ` Bruce Korb
2005-01-11 18:32 ` Marius Vollmer
2005-05-14 2:52 ` deprecated symbol warnings Ken Raeburn
2005-05-14 12:40 ` Neil Jerram
2005-05-14 18:48 ` Ken Raeburn
2005-05-15 3:17 ` John W. Eaton
2005-05-15 10:19 ` Neil Jerram
2005-05-16 5:52 ` Ken Raeburn
2005-05-18 4:22 ` tomas
2005-05-18 12:20 ` Ludovic Courtès
2005-05-18 17:17 ` automated testing (was Re: deprecated symbol warnings) Ken Raeburn
2005-05-26 18:58 ` deprecated symbol warnings Neil Jerram
2005-05-28 21:55 ` Ken Raeburn
2005-05-18 19:18 ` deprecated symbol warnings and Windows Ken Raeburn
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=lju0pnx2hi.fsf@troy.dt.e-technik.uni-dortmund.de \
--to=marius.vollmer@uni-dortmund.de \
--cc=guile-user@gnu.org \
--cc=mckelvey@users.sourceforge.net \
/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).