_DateTimeSplit never returns @error, and thus, any bad formated datetime will pass

[matwachich@…]

_DateTimeSplit doc states

Success: Date and Time into two separate Arrays. 
Failure: 0 and sets the @error flag to non-zero. 
@error: 1 - Invalid Input Date 

But you see the code of the function, the only return value is at the end and returns 1, without any error.

It seems that the function does not any check to the input string, so the documentation should not state that it does so.

I don't know if we should modify the documentation, or the function itself (makine it a bit more complexe to be able to check input).

[Melba23]

IMO the easiest way forward would be to add a single line to the function checking the date format:

If Not StringRegExp($sDate, "\d{4}[/.-]\d{2}[/.-]\d{2}[T ]\d{2}:\d{2}(:\d{2})?"( Then Return SetError(1, 0, 0)

But no doubt a real RegEx guru could come up with a better pattern.

M23

[Jos]

I think the documentation is wrong and shouldn't state that @error is returned as this function really is used as an helper function and not intended to check for validity of the date.
You need to use _DateIsValid() for that. (which uses this UDF).
This is all written a very long time ago so there most likely could be many improvements made now we indeed have regex to our disposal. :)

[Jpm]

I fix, I think, all your concerns "include" and doc about _DateIsvalid reference

[Jpm]

Fixed by revision [12502] in version: 3.3.15.4