shared-text substrings, start/end indices, xs><, etc. shivers@xxxxxx (25 Jan 2000 01:02 UTC)
Re: shared-text substrings, start/end indices, xs><, etc. sperber@xxxxxx (25 Jan 2000 07:47 UTC)
shared-text substrings shivers@xxxxxx (25 Jan 2000 16:06 UTC)
Re: shared-text substrings sperber@xxxxxx (25 Jan 2000 16:54 UTC)
Re: shared-text substrings shivers@xxxxxx (25 Jan 2000 17:15 UTC)
Re: shared-text substrings sperber@xxxxxx (25 Jan 2000 17:54 UTC)
Re: shared-text substrings shivers@xxxxxx (25 Jan 2000 19:18 UTC)
Re: shared-text substrings sperber@xxxxxx (26 Jan 2000 07:30 UTC)
Re: shared-text substrings, start/end indices, xs><, etc. d96-mst-ingen-reklam@xxxxxx (28 Jan 2000 12:41 UTC)

Re: shared-text substrings, start/end indices, xs><, etc. d96-mst-ingen-reklam@xxxxxx 27 Jan 2000 13:54 UTC

In article <200001250101.UAA10381@mongkok.smartleaf.com>,
xxxxxx@ai.mit.edu wrote:

>SRFI-13 is trying to walk a third path. I'm not willing to *require*
>shared-text substrings. That's just not going to happen out there in
>Scheme-land, at least we can't just mandate it. I'm just trying to allow
>people to write portable code that can run reasonably efficiently across a
>wide range of platforms -- some with shared-text substrings, some without.

You are allowing people to write ugly code to gain some efficiency,
without loosing portably.

But there is already a language for this: C. ANSI/ISO C is portable and
allows you to write very efficient string processing code.

Please don't destroy the nice language Scheme with such provisions for
ugly code as allowing string indexes in every string procedure.

--
/****************************************************************\
* You have just read a message from Mikael Ståldal.              *
*                                                                *
* Remove "-ingen-reklam" from the address before mail replying.  *
\****************************************************************/