Inconsistency in Date Formats Between @DATE and @MAKEDATE

Jun 2, 2008
386
2
Newton, MA
There is an inconsistency in the date format specifications between the
functions @DATE and @MAKEDATE. For @DATE, format 4 is defined as:

4 ISO (yyyy/mm/dd)


For @MAKEDATE it is:

4 ISO 8601 (yyyy-mm-dd)


In one case the separator is slashes; in the other it is hyphens. The
@MAKEDATE function does generate output with hyphens. The @DATE function
seems to accept either hyphens or slashes in the input.

If nothing else, the help files should be corrected.

-- Jay
 
May 20, 2008
3,515
4
Elkridge, MD, USA
Jay Sage wrote:
| There is an inconsistency in the date format specifications between
| the functions @DATE and @MAKEDATE. For @DATE, format 4 is defined as:
|
| 4 ISO (yyyy/mm/dd)
|
|
| For @MAKEDATE it is:
|
| 4 ISO 8601 (yyyy-mm-dd)
|
|
| In one case the separator is slashes; in the other it is hyphens. The
| @MAKEDATE function does generate output with hyphens. The @DATE
| function seems to accept either hyphens or slashes in the input.
|
| If nothing else, the help files should be corrected.

Look at topic "datefmt.htm" - it clearly explains that in date input almost
any nonnumeric character, including letters, is an acceptable separator. For
example, 2004m5.1 and 2004-05-01 are interpreted identically. Your concern
has been covered sinve the V6 issue of the help files.
--
Steve
 
Jun 2, 2008
386
2
Newton, MA
I still think that the help information should be consistent in the two
functions regarding what the ISO standard format #4 means. The fact that
input with other separators works does not change that. I'm not
complaining about the functions themselves, only about the help text.

-- Jay
 

Charles Dye

Super Moderator
Staff member
May 20, 2008
4,493
91
Albuquerque, NM
prospero.unm.edu
On a related note, I'd suggest doing a global search-and-replace for yyyy-www-d and replacing it with yyyy-Www-d (i.e. uppercase the first W to indicate that it is a literal letter W, not a placeholder for a digit.)
 
Similar threads
Thread starter Title Forum Replies Date
R Inconsistency in @version's use of quotes Support 2
jbanaszczyk help files: minor inconsistency Support 2
thedave BDEBUGGER vs not inconsistency Support 15
M If and Iff inconsistency... Support 9
D pdir inconsistency Support 4
old coot File create date/time is sticky across file deletion. Support 9
sully9 How to? Unexpected %DATE% CMD variable format (vs DATE /T format) in CMDebug Support 1
mfarah Fixed The DATE command produces the wrong error message. Support 1
T Date format date different from cmd Support 7
Jesse Heines How to? How to display picture creation date with dir command Support 6
Jesse Heines "Taken" date for JPG and PNG files Support 4
Joe Caverly DATE format 4 Support 7
fpefpe touch - date format Support 2
C 7zip with date range .vs. filelist created with dir and daterange Support 0
C How to? Add date/time to custom tpipe based BTM Support 1
vefatica Download center not up to date Support 4
Joe Caverly How to? Date Range in command line for 7zip /= Support 1
N date and cmd compatibility Support 10
rps Functions @year[date] @isowyear[date] help Support 7
S Closing date for V16 suggestions Support 1
JohnQSmith DATE /T Support 13
A How to? Create a date range based upon creation date Support 2
S How to? Command dialogs vs. size/date/etc. exclusion ranges Support 1
M How to? Effectively "combine" date and time ranges... Support 2
CWBillow Make a folder named Date-Time Support 18
vefatica Do UNTIL DATETIME date time Support 6
S Date range question Support 4
Roedy date range documentation error Support 2
dcantor More date-related help items for V11 Support 0
dcantor Help text for Date Formats Support 0
dcantor Suggestion for @DATE[] input Support 2
dcantor @DATE help example Support 0
CWBillow Date and Time in names Support 11
C Non-Jpsoft question (music file formats?) Support 0

Similar threads