Bug in exclude timeperiods code? (t-tap/test_timeperiods.c)

Ton Voon tonvoon at gmail.com
Mon Aug 9 11:26:02 CEST 2010


On 5 Aug 2010, at 13:43, nap wrote:

> Hi,
>
> I can't code, but I can propose an algorithm that works (optimal I
> don't know). It just need functions to get the start and end see from
> a time we want for all daterange types (maybe there are already theses
> functions).
>
> Then it' a recursive algo between valid/invalid (will always go
> thurser and stop at begining+1 year so it will stop). The "next
> invalid" function is like valid, for each daterange we search the next
> invalid, check is this time is globally invalid (can be invalid for a
> daterange but valid for another one) and take the min. Then check for
> it's own exclude of course (so next valid for them).
>
> I hope someone will code it.
>
>
> Jean

Hi Jean,

Can you clean up your test and add them as a TODO? This will help when  
we get round to coding it, to make sure it hits all the right cases.

As many different examples as possible would be great.

Ton


------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 




More information about the Developers mailing list