This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: strrstr
- From: "Carlos O'Donell" <carlos at systemhalted dot org>
- To: "Reuben Thomas" <rrt at sc3d dot org>
- Cc: libc-help at sourceware dot org
- Date: Fri, 2 May 2008 09:22:00 -0400
- Subject: Re: strrstr
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=0Yt5pe4fy5BoeDMNJeegwOKGc5qpHOAQOwkj6zWCQUU=; b=hkzt3tqRRl4cLNwioATarvI1maXB/95bodVyeKsoYVgKO808UKPvfulTEItwyUsBauplIEoqgjyzVPPC9jwbYr5CRSeTQiglmXm2yLMm8c8Y4pMfjJC7gL+iScaKM0bjoTrmChBjCUJDxZF2FukgPc2stPXx5tT1MyudueEQbAo=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=A+fxsM1ltcQsKPjir1vV0iNLcPWo/ofxNFWixwzWBmsi8jdfXtB/7Zt0JL5XvJTfYshQ4JsvI11h1A0FYQjUeuVFSwlsbHWzPEestRn90tg7CM+tR62zThTltuoM7C+ACGoXhGgCzOMiVcP5i/e7D+JzlPfmwDgvbua9rqUqULA=
- References: <alpine.DEB.1.00.0804302028360.19137@canta> <20080430204909.D4E8926FA04@magilla.localdomain> <alpine.DEB.1.00.0804302245270.6734@canta>
On Wed, Apr 30, 2008 at 6:10 PM, Reuben Thomas <rrt@sc3d.org> wrote:
> It fills an obvious gap in the API (strchr, strrchr; strstr, strrstr), and
> has the same semantics and name pretty much everywhere, so there's no
> contention to resolve in what it should be called or do.
I'm CC'ing libc-help in order to continue this dicussion.
If you are really interested in adding reverse search variants to the
API you will need to do a little leg work.
1. What other C libraries implement these functions?
2. How does relying on these functions effect portability between OSs?
3. Are all the strrstr's the same? Do you have a test suite which
shows they are the same?
4. Does your strrstr support all the new character types being
proposed by TR 19769 for the C standard?
There is a big gap between inspiration and implementation :-)
Cheers,
Carlos.