Re: [reSIProcate] v1.9 and fixed-size integer types (UInt32, uint32_t, etc)
On 10/09/13 17:02, Scott Godin wrote:
> This #ifdef wouldn't be based on user controlled definitions - I don't
> think it will have the same issues as the reflow/recon problems, where
> you build one library with a particular set of flags that differ from
> other parts of the application. We use platform based #ifdefs in many
> places (ie: Condition.hxx, DnsUtil.hxx, Mutex.hxx ).
>
Ok, that type of thing is fine if it is for all users on a particular
platform (e.g. all WIN32 rather than just all Visual Studio users)
> I'm all for easing upgrades if it's possible and safe. For now I will
> commit the casting fix to make WinCompat.cxx compile and we can see
> how the feedback is as trunk get's used further.
Here you can see how I was planning to bring in the stdint stuff, I just
don't know how widely this will impact other users but it does work for me:
http://list.resiprocate.org/archive/resiprocate-commit/msg07468.html
and in particular, see:
http://svn.resiprocate.org/viewsvn/resiprocate/branches/b-pocock-stdint/rutil/compat.hxx?r1=10313&r2=10314&diff_format=l
- References:
- [reSIProcate] v1.9 and fixed-size integer types (UInt32, uint32_t, etc)
- Re: [reSIProcate] v1.9 and fixed-size integer types (UInt32, uint32_t, etc)
- Re: [reSIProcate] v1.9 and fixed-size integer types (UInt32, uint32_t, etc)
- Re: [reSIProcate] v1.9 and fixed-size integer types (UInt32, uint32_t, etc)
- Re: [reSIProcate] v1.9 and fixed-size integer types (UInt32, uint32_t, etc)
- Re: [reSIProcate] v1.9 and fixed-size integer types (UInt32, uint32_t, etc)
- Re: [reSIProcate] v1.9 and fixed-size integer types (UInt32, uint32_t, etc)
- Re: [reSIProcate] v1.9 and fixed-size integer types (UInt32, uint32_t, etc)