LIST-EXT and list_data rewrite

2011-06-30 Thread Bron Gondwana
I've been looking at various bugs with LIST throughout 2.4.x, with different LSUB and LIST and stuff issues. Most of them are now fixed in stable and in master, but there's still some things that the dovecot 'imaptest' tool finds. The core problem is this: we have two functions,

Re: Coding standards for 32/64-bits data

2011-06-30 Thread OBATA Akio
On Wed, 29 Jun 2011 22:32:23 +0900, Bron Gondwana br...@fastmail.fm wrote: On Wed, Jun 29, 2011 at 02:21:17PM +0200, Julien Coloos wrote: Hi there, I am currently wondering how to properly handle (ex-32/)64-bits data in cyrus code. Since this may be useful for other developpers willing to

Re: Coding standards for 32/64-bits data

2011-06-30 Thread Bron Gondwana
On Thu, Jun 30, 2011 at 10:54:43PM +0900, OBATA Akio wrote: For ticket 3376 (time_t != unsigned long), I would be helpful if TIME_T_FMT is also introduced. (or use fixed type (uint64_t?) for network protocol/database timestamp instead of time_t?) To be honest, you can mostly use uint32_t

Re: Coding standards for 32/64-bits data

2011-06-30 Thread Bron Gondwana
On Fri, Jul 01, 2011 at 10:46:05AM +0900, OBATA Akio wrote: I want to clear following issue before NetBSD-6.0 release. http://gnats.netbsd.org/44275 Then, workaround until 32-bits time_t overflow is cast to `unsigned long' time_t data to pass snprintf with %lu format? I can find it in