vector->range issues
Wolfgang Corcoran-Mathe
(01 Sep 2020 19:21 UTC)
|
Re: vector->range issues
Marc Nieper-Wißkirchen
(01 Sep 2020 19:28 UTC)
|
Re: vector->range issues
Wolfgang Corcoran-Mathe
(01 Sep 2020 20:52 UTC)
|
Re: vector->range issues
Marc Nieper-Wißkirchen
(02 Sep 2020 05:48 UTC)
|
Re: vector->range issues
Marc Nieper-Wißkirchen
(02 Sep 2020 07:57 UTC)
|
string-range
Marc Nieper-Wißkirchen
(02 Sep 2020 13:14 UTC)
|
Re: string-range Wolfgang Corcoran-Mathe (02 Sep 2020 14:50 UTC)
|
Re: string-range
Marc Nieper-Wißkirchen
(02 Sep 2020 15:01 UTC)
|
Re: string-range
Wolfgang Corcoran-Mathe
(02 Sep 2020 15:56 UTC)
|
Re: string-range
Marc Nieper-Wißkirchen
(02 Sep 2020 15:58 UTC)
|
Re: string-range
John Cowan
(02 Sep 2020 21:12 UTC)
|
Re: string-range
Wolfgang Corcoran-Mathe
(02 Sep 2020 21:16 UTC)
|
Re: string-range
Wolfgang Corcoran-Mathe
(02 Sep 2020 21:25 UTC)
|
Re: vector->range issues
Wolfgang Corcoran-Mathe
(02 Sep 2020 14:46 UTC)
|
On 2020-09-02 15:14 +0200, Marc Nieper-Wißkirchen wrote: > In this spirit, I would also want to suggest > > (string-range STRING) > > a range constructor that takes a string and does the obvious thing. As > with vector-range, the argument mustn't be modified later. > > [snip] > > The nice thing is it is transparent for the user who just wants to > examine a string character-wise. He or she just has to work with > (string-range s) instead of s directly. Excellent points, I like it. Added to my repository. Thanks very much. -- Wolfgang Corcoran-Mathe <xxxxxx@sigwinch.xyz> "Karate begins with courtesy and ends with it." --Shoshin Nagamine