By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

Request for documentation for ISO8601 plugin


[This was originally sent in email last month.]

Quite by accident, due to a typo on my part, I discovered that
the word 'TODAY' works just as well as a solitary 'T' in a time
specification. TODAY+1 works, TODAY-1 works, too.

So, first I thought perhaps anything beginning with T would work the
same as a solitary T, but I tried TOMORROW and TRUE, and both produced
an invalid argument error.

So I conclude that you must have purposely allowed the word

I discovered this because I had an environment variable TODAY,
which stood for the processing date, not the current date, in a
.bat file and had coded %@dateconv[today,,20]. The .bat file
kept coming up with the wrong answer, and I finally figured out
that I omitted the '%'! (Yes, TODAY is a lousy name for that -- and
I changed it to PROCDATE.)

I could not find any reference to the full word TODAY in the
documentation for ISO8601, but I like it. I would use it to make my
files more readable (like %@dateconv[TODAY+7,,20], e.g.), but I don't
want to do that if it's likely that the feature may disappear.

So I'm asking that if you intend to keep allowing this syntax,
you add it to the documentation next time you update the plugin.
I'll have to look at the code and decide whether that was intentional or not. I don't remember allowing that, but my plugins tend to have a metric buttload of undocumented features.
There are no imperial buttloads, only imperial bumloads.

1 metric buttload ≈ 1.10 US (short) buttloads
1 metric buttload ≈ 0.984 imperial (long) bumloads
[FOX] Ultimate Translator