apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject Re: cvs commit: apr-util/crypto apr_md5.c
Date Wed, 22 Jan 2003 03:44:24 GMT
At 09:15 PM 1/21/2003, 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.  

How?

>Do we need to
>bump a version number or do some magic to make our binary compat
>people happy?  -- justin

Not if it doesn't.  I can't conceive of a platform which would.  We are
already casting between point types to byte buffers, it's just a simple
pointer.  No incompatibility.

Bill  


Mime
View raw message