# time parsing in 7.1

**URL:** <https://forum.mikrotik.com/t/time-parsing-in-7-1/154185>\
**Category:** Scripting\
**Created:** [December 15, 2021, 5:46pm UTC](https://forum.mikrotik.com/t/time-parsing-in-7-1/154185 "2021-12-15T17:46:34Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Sob](https://forum.mikrotik.com/letter_avatar/sob/32/6_449c533f586939b6e5f246632a46421f.png) [@Sob](https://forum.mikrotik.com/u/Sob)\
**Post date:** [June 2, 2022, 2:32am UTC](https://forum.mikrotik.com/t/time-parsing-in-7-1/154185/7 "2022-06-02T02:32:18Z")

</div>

What I don’t understand is how MikroTik can watch for years, how people have to write crazy long scripts for basic operations, and not think “hmm, maybe we could add some functions for that?” (to be fair, they [did have that thought](http://forum.mikrotik.com/t/built-in-function-library/117288/1), but didn’t get beyond that). Isn’t it obvious enough that such functions would be useful and appreciated? Regarding time, why can’t we do things like [:totime “2022-06-02 04:15:30”], [:dateformat “Y-m-d H:i:s” [:timestamp]] (borrow the format e.g. from PHP’s date() function), etc?

---

_[View the full topic](https://forum.mikrotik.com/t/time-parsing-in-7-1/154185)._
