The obvious caveat to all of this is, in order to fix the saving of a
pointer into the hash table values, we are going to have to break binary
compatibility anyways, I just see no way around it other than ifdefing
this change to 64bit only.. so the answer may be, we totally break
binary compatibili
Hello,
On Tue, 29 Aug 2006, Michael Jerris wrote:
[ if (url->url_port) rv += (int)strlen(url->url_port) + 1; /* plus ':' */ ]
> I don't disagree with you, but the other option is to change the api to
> use size_t instead of int all over the place, which I am told is not
> really an option as it
I don't disagree with you, but the other option is to change the api to use
size_t instead of int all over the place, which I am told is not really an
option as it would totally break ABI. In this case, if the url_port is really
over the length of max int then you will indeed have a problem, bu
В Пнд, 28/08/2006 в 20:50 -0400, Michael Jerris пишет:
> + if (url->url_port) rv += (int)strlen(url->url_port) +
> 1; /* plus ':' */
Sorry, but this (int)strlen doesn't seems like a correct thing to me.
Probably it indicates different problems somewhere outside.
signature.asc
Descr
