Re: feature request-- [epoch]
This WebDNA talk-list message is from 2004
It keeps the original formatting.
numero = 55508
interpreted = N
texte = Here are some relative comments I found from another source: --begin comments Hi Norm, > In trying to work with the XML export from SourceForge, I see that > they store dates in the XML as seconds-since-1970. How quaint. > Anyway, this is actually a useful form sometimes. I wonder if it > makes sense to add: > > date:epoch-time() - returns the number of seconds since the epoch > (on Unix systems, the current epoch starts on Jan 1, 1970 at 00:00:00 GMT) > > date:epoch-time-to-date-time(int seconds) - returns a date-time for > a number of seconds > > date:date-time-to-epoch-time(string date-time) - does the inverse Currently, if you pass a date-time string to the date:seconds() function, then it gives you the number of seconds since 1970-01-01T00:00:00. So date:seconds() works as date:date-time-to-epoch-time() as above. What's more, if you call date:seconds() without an argument, it acts on the current date-time, so in fact date:seconds() without an argument is the same as date:epoch-time() as above. You can do date:epoch-time-to-date-time() by turning the number of seconds into a duration and adding that to the start of the epoch, as in: date:add('1970-01-01T00:00:00', date:duration($seconds)) Perhaps that's worth a shorthand -- possibly date:date-time() should have an optional argument, being a number of seconds since 1970-01-01T00:00:00 -- I'm not sure. There's an argument that date:seconds() shouldn't be overloaded, and shouldn't be tied to a particular epoch, especially the computer-oriented one of 1970-01-01T00:00:00 (Mike suggested Julian dates instead), but my feeling was (and is) that it's a common enough representation that it's worthwhile to support it specifically. For other epochs, you could use: date:seconds(date:difference($epoch, $date-time)) -- end coments -- =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o DONOVAN D. BROOKE Eucalyptus Design <-Web Development (specializing in eCommerce), -> <-Graphic Design, and Pre-Press Consultation -> ADDRESS:> Donovan Brooke DBA Eucalyptus Design N2862 Summerville Park Rd. Lodi, WI 53555 PH:> 1.608.592.3567 Web:> http://www.euca.us =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Here are some relative comments I found from another source: --begin comments Hi Norm, > In trying to work with the XML export from SourceForge, I see that > they store dates in the XML as seconds-since-1970. How quaint. > Anyway, this is actually a useful form sometimes. I wonder if it > makes sense to add: > > date:epoch-time() - returns the number of seconds since the epoch > (on Unix systems, the current epoch starts on Jan 1, 1970 at 00:00:00 GMT) > > date:epoch-time-to-date-time(int seconds) - returns a date-time for > a number of seconds > > date:date-time-to-epoch-time(string date-time) - does the inverse Currently, if you pass a date-time string to the date:seconds() function, then it gives you the number of seconds since 1970-01-01T00:00:00. So date:seconds() works as date:date-time-to-epoch-time() as above. What's more, if you call date:seconds() without an argument, it acts on the current date-time, so in fact date:seconds() without an argument is the same as date:epoch-time() as above. You can do date:epoch-time-to-date-time() by turning the number of seconds into a duration and adding that to the start of the epoch, as in: date:add('1970-01-01T00:00:00', date:duration($seconds)) Perhaps that's worth a shorthand -- possibly date:date-time() should have an optional argument, being a number of seconds since 1970-01-01T00:00:00 -- I'm not sure. There's an argument that date:seconds() shouldn't be overloaded, and shouldn't be tied to a particular epoch, especially the computer-oriented one of 1970-01-01T00:00:00 (Mike suggested Julian dates instead), but my feeling was (and is) that it's a common enough representation that it's worthwhile to support it specifically. For other epochs, you could use: date:seconds(date:difference($epoch, $date-time)) -- end coments -- =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o DONOVAN D. BROOKE Eucalyptus Design <-Web Development (specializing in eCommerce), -> <-Graphic Design, and Pre-Press Consultation -> ADDRESS:> Donovan Brooke DBA Eucalyptus Design N2862 Summerville Park Rd. Lodi, WI 53555 PH:> 1.608.592.3567 Web:> http://www.euca.us =o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o=o ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Donovan Brooke
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
PCS Frames-Default page is solution! (1997)
Locking up with WebCatalog... (1997)
WebCatalog stalls (1998)
Nesting format tags (1997)
Blocking form spam (2006)
Separate SSL Server (1997)
Physical Security for WebCatalog Directories (1997)
Cart ID Duplication (2001)
[isfile] ? (1997)
Hiding HTML in an [include] file... (2004)
JavaScript Image Problem (1998)
Summing fields (1997)
[WebDNA] GREP question (2010)
WebCat2b13 Mac plugin - [sendmail] and checkboxes (1997)
AutoCommit Preference? (1998)
Using Cookie for client specific info? (1997)
system crashes, event log (1997)
RSS Feed (2004)
carriage returns in data (1997)
Email notification to one of multiple vendors ? (1997)