RE: Issue with finding next DST change, date math error?

> From: Zefram [mailto:[email protected]] 
>
> The form of epoch seconds implemented by DateTime doesn't count
> leap seconds.  So in the time scale supplied by DateTime it is *not*

I wasn't aware of the bit about epoch Zefram pointed out.  Can someone answer this related hypothetical for me?

1. You create a date based on a static value, including TZ & DST considerations.
2. You perform date arithmetic which includes leap seconds.
3. You convert said result to epoch time.

If I understand Zefram correctly, then the result would not be an accurate representation of the true # of seconds since epoch, correct?

Thanks,

Bobby