Re: Date-fix (was: GnuCash XML spec)

2012-11-09 Thread John Ralls
On Nov 9, 2012, at 2:22 PM, John Ralls wrote: > > On Nov 9, 2012, at 12:41 PM, "Derek Atkins" wrote: > >> John, >> >> On Fri, November 9, 2012 2:47 pm, John Ralls wrote: >>> >>> Any objections to converting all Timespecs to time_t64? (I decided that >>> time_t64 is clearer than gnc_time_t.)

Re: Date-fix (was: GnuCash XML spec)

2012-11-09 Thread John Ralls
On Nov 9, 2012, at 2:46 PM, Derek Atkins wrote: > > On Fri, November 9, 2012 5:22 pm, John Ralls wrote: > >>> How about storing it in the book, and storing it as a pair of Month/Day >>> tuples? :) This also maps nicely into "current Period" and "last >>> Period". :) >> >> How about what t

Re: Date-fix (was: GnuCash XML spec)

2012-11-09 Thread Derek Atkins
On Fri, November 9, 2012 5:22 pm, John Ralls wrote: >> How about storing it in the book, and storing it as a pair of Month/Day >> tuples? :) This also maps nicely into "current Period" and "last >> Period". :) > > How about what the government calls a "Julian Day", the number of days > after

Re: Date-fix (was: GnuCash XML spec)

2012-11-09 Thread John Ralls
On Nov 9, 2012, at 12:41 PM, "Derek Atkins" wrote: > John, > > On Fri, November 9, 2012 2:47 pm, John Ralls wrote: >> >> Any objections to converting all Timespecs to time_t64? (I decided that >> time_t64 is clearer than gnc_time_t.) > > As opposed to time64_t? Maybe. There's int64_t in sys/

Re: Date-fix (was: GnuCash XML spec)

2012-11-09 Thread Derek Atkins
John, On Fri, November 9, 2012 2:47 pm, John Ralls wrote: > > Any objections to converting all Timespecs to time_t64? (I decided that > time_t64 is clearer than gnc_time_t.) As opposed to time64_t? > Another issue which I just discovered is that we're using GConf to store > time_t values for the

Re: Date-fix (was: GnuCash XML spec)

2012-11-09 Thread John Ralls
On Nov 6, 2012, at 7:28 AM, John Ralls wrote: > > I'm keeping Timespec/GncDate for now because I'm not ready to redo all of the > Timespec-based code in engine. Similarly, I wrote gnc_localtime etc as a > drop-in replacement for g_localtime and friends. That's the only way I'm > going to be

Re: Git migration - github vs code.gnucash.org

2012-11-09 Thread David Goodenough
On Friday 09 Nov 2012, Derek Atkins wrote: > Ngewi Fet writes: > > On Tue, Nov 6, 2012 at 4:09 PM, Derek Atkins wrote: > > John Ralls writes: > > > Why can't we set up commit hooks on each that immediately push to > > > the other? Yes, there's a small chance of a conflict if two peop

Re: Git migration - github vs code.gnucash.org

2012-11-09 Thread Derek Atkins
Ngewi Fet writes: > On Tue, Nov 6, 2012 at 4:09 PM, Derek Atkins wrote: > > John Ralls writes: > > > Why can't we set up commit hooks on each that immediately push to the > > other? Yes, there's a small chance of a conflict if two people push > > changes of the same file to