< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

RE: [reSIProcate] u_int32_t


OK - done now!  I changed the usages of u_int32_t in BerkleyDB.cxx to
grab u_int32_t from global scope (ie.  ::u_int32_t) - hopefully this is
OK for all platforms.

Scott

> -----Original Message-----
> From: stensil [mailto:stensil@xxxxxxx]
> Sent: Wednesday, October 19, 2005 7:13 AM
> To: Scott Godin
> Cc: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [reSIProcate] u_int32_t
> 
> Be careful with the repro-sources after that ;)
> In the BerkeleyDB.cxx u_int32_t-typedef from berkeley DB sources and
> resip::u_int32_t will conflict... I don't see simple solution for that
> situation except removing line "using namespace resip" in
BerkeleyDB.cxx
> and *explicit* using resip namespace all over this file, but this is
so
> ugly... :s
> 
> Scott Godin wrote:
> > Oops - I missed the end bracket on the namespace definition - I'll
fix
> it
> > later today.  Thanks for catching that.  : )
> >
> > -----Original Message-----
> > From: stensil [mailto:stensil@xxxxxxx]
> > Sent: Wednesday, October 19, 2005 5:46 AM
> > To: Scott Godin
> > Cc: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [reSIProcate] u_int32_t
> >
> > :-?  It seems to me that u_int32_t-typedef is located in global
> > namespace as yet...
> >
> > Scott Godin wrote:
> >
> >> I moved it to the resip namespace in SVN head.
> >>
> >>
> >>
> >>> -----Original Message-----
> >>> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> >>>
> >>>
> >> [mailto:resiprocate-
> >>
> >>
> >>> devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of stensil
> >>> Sent: Tuesday, October 18, 2005 12:15 AM
> >>> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> >>> Subject: [reSIProcate] u_int32_t
> >>>
> >>> Hello, in rutil/compat.hxx for WIN32-platform there is typedef
> >>>
> >>>     typedef unsigned int u_int32_t; //!dcm! -- any other
platforms?
> >>>
> >>> which conflicts with u_int32_t in JRTPLib :(
> >>> Maybe just put this typedef in resip-namespace?..
> >>>