umgeher/qdate
0
Fork 0
Code Issues Pull requests Releases Activity

README fix

Browse source
This commit is contained in:
Jesse Gumm 2013-04-29 22:28:39 -05:00
parent b602984931
commit d59447db2f
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.markdown
View file

@ -144,13 +144,13 @@ be attempted before engaging the `ec_date` parser.
+ `deregister_format(Key)` - Deregister the formatting string from the + `deregister_format(Key)` - Deregister the formatting string from the
`qdate` server. `qdate` server.
## About backwards compatibility with `ec_date` and deterministic parsing ### About backwards compatibility with `ec_date` and deterministic parsing
`ec_date` and `dh_date` both have a quirk that bothers me with respect to the `ec_date` and `dh_date` both have a quirk that bothers me with respect to the
parsing of dates that causes some date parsing to be *non-deterministic*. That parsing of dates that causes some date parsing to be *non-deterministic*. That
is, if parsing an incomplete date or time (ie, a text string that is missing a is, if parsing an incomplete date or time (ie, a text string that is missing a
time or a date), `ec_date` will automatically insert the current values of time or a date), `ec_date` will automatically insert the current values of
those. those as read by the system clock.
For example, if the following lines are run a few seconds apart: For example, if the following lines are run a few seconds apart:
@ -177,7 +177,7 @@ parsed datetime has the date inferred from the current date. Admittedly,
inferring the date bothers me less than inferring the time, but in the name of inferring the date bothers me less than inferring the time, but in the name of
consistency, there should be options for enabling or disabling both. consistency, there should be options for enabling or disabling both.
### The Solution For Both #### The Solution For Non-deterministic parsing
To solve this issue for users that are bothered by this, while preserving To solve this issue for users that are bothered by this, while preserving
backwards compatibility for folks who prefer this, we're going to introduce a backwards compatibility for folks who prefer this, we're going to introduce a