Hello, On 12/10/06, Dale R. Worley <[EMAIL PROTECTED]> wrote: > As I mentioned some while ago, I'm going to change the typedefs used for > 64-bit integers to Int64 (signed) and UInt64 (unsigned). These will > replace the several different typedefs that are now being used in > different branches (and all of which violate the coding guidelines). Is there any reason to use custom type names instead of ANSI C9x standartized (u)int*_t types? This types provided by most new compilers. For older compilers that does not support C9x workarounds could be created. One of portable stdint.h replacements could be find here: http://www.azillionmonkeys.com/qed/pstdint.h And I wrote one other stdint.h (and inttypes.h) for Visual Studio.
> For most developers, this should make no difference -- once I check in > the changes, your next "svn update" will patch all your files. > > But there are some large-scale merging efforts going on, and I want to > make sure that I don't cause them extra work. So I need some > information: > > 1) What branches are you using for development? (other than "main") > > 2) Will a consistent change of these typedefs on all active branches > interfere with contemplated merges? sipXtapi-media-update is synchronized to sipXtapi branch. I did not use 64 bit integers in new code, so this change should gone seamlessly for sipXtapi-media-update branch. -- Regards, Alexander Chemeris. _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
