Ben Reser wrote:
>On Fri, Feb 27, 2004 at 12:39:54AM +0100, Branko ??ibej wrote:
>
>
>>If the bindings in 1.0.0 don't work, that's sad of course, but it's not
>>the end of the world. Presumably the problem will be fixed in time for
>>1.0.1, just like any other bug. I don't consider this to be a big enough
>>problem to yank 1.0.0, or to rush into 1.0.1.
>>
>>
>
>I really dislike having binaries up that don't work. If it doesn't work
>it shouldn't be posted. People depending on the bindings for viewcvs
>are going to upgrade under the presumption that everything they need is
>ready to upgrade...
>
>
That's what the issue tracker is for.
>>Besides, from looking at the suggested patches, this doesn't look like a
>>Windows-specific problem to me at all -- nor is the fix correct.for all
>>platforms. Taking a quick glance at apr's configure.in, I see that
>>APR_INT64_T_FMT can be any one of d, ld, lld, or qd on Unix-like
>>systems. FreeBSD+Linux != Unix, everything else != Windows.
>>
>>
>
>I don't have access to systems using "d" or "qd". So I have no idea if
>they're generating warnings or not. However, the current patch will
>still work on those platforms. It just may have a warning about the
>format not matching the type exactly.
>
Think what happens with an 128-bit long int... :-)
>If someone wants to make
>suggestions on fixes for warnings on other platforms I'm open to
>applying them.
>
>
The patch is Python-specific; Python defines PY_LONG_LONG, so I'd expect
we'd always map 64-bit types to that.
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 27 07:41:24 2004