| Summary: | ASTERISK-00469: DateTime order is wrong | ||
| Reporter: | puzzled (puzzled) | Labels: | |
| Date Opened: | 2003-10-31 13:44:43.000-0600 | Date Closed: | 2011-06-07 14:05:18 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | CVS from 10/27. DateTime says: october 31, 8:11pm, 2003. I think the order is wrong. Shouldn't that be: october 31, 2003, 8:11pm? ****** ADDITIONAL INFORMATION ****** relevant part in extensions.conf: exten => 13,1,Wait(1) exten => 13,2,DateTime() exten => 13,3,Wait(2) exten => 13,4,DateTime() exten => 13,5,Wait(2) exten => 13,6,Hangup | ||
| Comments: | By: Tilghman Lesher (tilghman) 2003-11-01 15:30:23.000-0600 Use SayUnixTime() instead. Without arguments, it says the current time in standard format in the machine's timezone. Format, time, and timezone may all be optionally specified. By: John Todd (jtodd) 2003-12-02 14:20:51.000-0600 So, is DateTime defunct? Should it be deprecated in favor of SayUnixTime? While DateTime still perhaps has the aforementioned bug, maybe we should see if mark would want to just remove DateTime after some months of notice, or perhaps hack it into SayUnixTime with a pre-defined format. By: Tilghman Lesher (tilghman) 2003-12-02 16:23:46.000-0600 SayUnixTime could be made to register itself as both SayUnixTime as well as DateTime, a la Voicemail and Voicemail2. It has a superset of DateTime in functionality, although with no arguments, it does the same thing as DateTime (as DateTime takes no arguments). However, DateTime does serve a purpose in CVS: it is a fairly simple application that could serve as a model (a jumping off point) to future application programmers. | ||