This is the mail archive of the
glibc-bugs@sources.redhat.com
mailing list for the glibc project.
[Bug libc/166] strcasestr.c with local support (partial solution shown)
- From: "Digital at JoesCat dot com" <sourceware-bugzilla at sources dot redhat dot com>
- To: glibc-bugs at sources dot redhat dot com
- Date: 18 May 2004 01:28:40 -0000
- Subject: [Bug libc/166] strcasestr.c with local support (partial solution shown)
- References: <20040516084644.166.Digital@JoesCat.com>
- Reply-to: sourceware-bugzilla at sources dot redhat dot com
------- Additional Comments From Digital at JoesCat dot com 2004-05-18 01:28 -------
Subject: Re: strcasestr.c with local support (partial solution shown)
On Monday 17 May 2004 12:45, pere at hungry dot com wrote:
>------- Additional Comments From pere at hungry dot com 2004-05-17 19:45
> ------- Can you explain how this patch is supposed to change the
> behavoiur of strcasestr()? It would be easier to evaluate it if the
> intention was explicitly stated.
Sorry, I haven't really figured out bugzilla to have included the details
as attachments, plus I've run into these enter boxes where there is a
limit of 4000 characters or something like that, therefore clipping-out
further important information (I did not want it to clip info, therefore
that is why the brief diff solution).
Thank you for replying as you have more experience dealing with and
inserting attachments into bugzilla (I hope).
Looking at glib, I notice that there is localized equivalents to strcase
functions (note the added _l to examples below):
glibc-2.3.2/sysdeps/generic/strcasecmp.c
glibc-2.3.2/sysdeps/generic/strcasecmp_l.c
glibc-2.3.2/sysdeps/generic/strncase.c
glibc-2.3.2/sysdeps/generic/strncase_l.c
It appears that strcasestr.c is the only exception without an _l
equivalent, so I was suggesting also adding an _l version for strcasestr.c
because it also is a strcase type function.
so:
glibc-2.3.2/sysdeps/generic/strcasestr.c
becomes:
glibc-2.3.2/sysdeps/generic/strcasestr.c
glibc-2.3.2/sysdeps/generic/strcasestr_l.c
If I use strncase.c and strncase_l.c as a template example, then this is
the expected results (I hope, but think I may be missing information):
diff.txt
version 2.3.2 -> improved version shown in bug126
diff_.txt
improvement version shown in bug126 -> "_l" version
strcasestr.c
this includes bug126 improvement plus _l changes I hope gets inserted
(I used strncase.c as template example for this)
(I am not sure about the undef __strcasestr since I do not know how to
compile the glib libraries yet)
strcasestr_l.c
(new file required if I follow strncase.c as example)
diff_.txt
here is the diff_.txt between the previous improvement suggested in bug 126
and the new improved strcasestr.c with _l added
(no longer important since you see accumilated changes in strcasestr.c
attached).
I believe the string.h files need to be updated as well to include
recognition for strcasestr_l but was unsure where to put it since you may
have some sort of "order' which you would prever to keep it in.
Then there needs to be some way to include the new strcasestr_l when
compiling the entire library, but since i'm not sure where to look yet,
I'm hoping that you have more experience in knowing where to activate it.
Sorry about an incomplete solution, but I hope my bug166 allows you to be
aware that maybe strcasestr could be improved for local functionality :-)
question:
BTW did bug 126 get included?
I don't know where to look for the upgraded libraries - that is if it
actually got included ???.
Thanks,
I hope this helps, but if you need more info, please reply.
------- Additional Comments From Digital at JoesCat dot com 2004-05-18 01:28 -------
Created an attachment (id=84)
--> (http://sources.redhat.com/bugzilla/attachment.cgi?id=84&action=view)
------- Additional Comments From Digital at JoesCat dot com 2004-05-18 01:28 -------
Created an attachment (id=85)
--> (http://sources.redhat.com/bugzilla/attachment.cgi?id=85&action=view)
------- Additional Comments From Digital at JoesCat dot com 2004-05-18 01:28 -------
Created an attachment (id=86)
--> (http://sources.redhat.com/bugzilla/attachment.cgi?id=86&action=view)
------- Additional Comments From Digital at JoesCat dot com 2004-05-18 01:28 -------
Created an attachment (id=87)
--> (http://sources.redhat.com/bugzilla/attachment.cgi?id=87&action=view)
------- Additional Comments From Digital at JoesCat dot com 2004-05-18 01:28 -------
Created an attachment (id=88)
--> (http://sources.redhat.com/bugzilla/attachment.cgi?id=88&action=view)
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=166
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.