Branko Čibej wrote:
> Justin Erenkrantz wrote:
> 
> 
>>--On Tuesday, January 21, 2003 8:27 PM +0000 gstein@apache.org wrote:
>>
>>
>>>  @@ -145,7 +145,7 @@
>>>    * @param inputLen The length of the next message block
>>>    */
>>>   APU_DECLARE(apr_status_t) apr_md5_update(apr_md5_ctx_t *context,
>>>-                                         const unsigned char 
>>
>>*input,
>>
>>
>>>+                                         const void *input,
>>>                                         apr_size_t inputLen);
>>>   /**
>>
>>
>>My hunch is that this breaks binary compatibility.  Do we need to
>>bump a version number or do some magic to make our binary compat
>>people happy?  -- justin
>>
> 
> It shouldn't. It could only break binary compatibility on systems where
> the representation and/or size of a void* is different than the
> representation of a char*, and I bet APR doesn't work on such systems.

The representation is not _allowed_ to be different.

Cheers,

Ben.

-- 
http://www.apache-ssl.org/ben.html       http://www.thebunker.net/

"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit." - Robert Woodruff