Time.parse does not throw ArgumentError on all invalid arguments
When Time.parse is not able to parse certain strings into valid Time objects, it does not throw ArgumentErrors. Instead, it returns Time.now.
For example, Time.parse("asdf") returns Wed Jul 16 17:03:19 -0400 2008.
This is observed on Mac OS X 10.5.3 running on a power pc and on Ubuntu 8.04 running ruby 1.8.6.
Updated by shyouhei (Shyouhei Urabe) about 11 years ago
- Status changed from Open to Rejected
Yes. That's an expected behavior.
Time.parse ignores what cannot be a time representation (ex.
Time.parse("it's 18:00") #=> Time object of 18:00 today), and
Time.parse("") is designed to be Time.now, hence the result.