[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-users] utc-time->seconds and local-time->seconds rationale?
From: |
Michele La Monaca |
Subject: |
[Chicken-users] utc-time->seconds and local-time->seconds rationale? |
Date: |
Sun, 4 May 2014 20:44:18 +0200 |
Hi,
I am not an expert here, but I find these functions ill-defined.
Both take as input a time-vector which already carries the timezone
information (seconds west of UTC). So a "time->seconds" function just
seems the right thing to me. Having to specify the local/utc prefix
feels redundant, confusing and error-prone:
(local-time->seconds (seconds->utc-time 0)) -3600.0
(utc-time->seconds (seconds->local-time 0)) 3600.0
Regards,
Michele
- [Chicken-users] utc-time->seconds and local-time->seconds rationale?,
Michele La Monaca <=
- Re: [Chicken-users] utc-time->seconds and local-time->seconds rationale?, Michele La Monaca, 2014/05/06
- Re: [Chicken-users] utc-time->seconds and local-time->seconds rationale?, John Cowan, 2014/05/07
- Re: [Chicken-users] utc-time->seconds and local-time->seconds rationale?, Michele La Monaca, 2014/05/07
- Re: [Chicken-users] utc-time->seconds and local-time->seconds rationale?, John Cowan, 2014/05/07
- Re: [Chicken-users] utc-time->seconds and local-time->seconds rationale?, Michele La Monaca, 2014/05/07