[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Issue 1031 (gcc3.3 compile warnings) is out of date

From: David Waite <mass_at_akuma.org>
Date: 2003-02-06 18:18:15 CET

I started to check the gcc mainline errors against the known errors on
3.3, and wound up getting distracted and just fixing most of the
warnings in my own tree. :-) libsvn_delta was the one library I didn't
want to touch, since I didn't have cscope set up at the time, so I
couldn't examine how the functions were actually used.

I'm unfamiliar with svn_filesize_t; why is it signed, and what
differentiates it from apr_off_t?

The Visual Studio.Net compiler can also generate warnings if types would
not match due to variation of size on a 64 bit platform, which is rather
cool.

-David Waite

Branko Čibej wrote:

>Jani Monoses wrote:
>
>
>
>>I looked at warnings generated by 3.3 a couple of days back and most seem
>>to be unsigned signed comparison related as Julian said.And they were about apr_size_t
>>and apr_off_t maybe when the filesize_t issue is done they'll go away.
>>
>>
>>
>Yes, but only because I'll do some judicious warning cleanup at the same
>time. :-) svn_filesize_t will be signed; apr_size_t isn't. There's also
>a whole mess of warnings on Windows which you don't see on most Unices,
>because apr_off_t is 64 bits wide on Windows.
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 6 18:23:37 2003

This is an archived mail posted to the Subversion Dev mailing list.