Pre 4.4 - ';' (command separator) was ignored by time
# time; echo hola
-bash: syntax error near unexpected token `echo'Why would you want to time nothing? What does it output, real 0s user 0s system 0s?
Re:Bash 4.4 released
by thiagoharry on Friday September 16, 2016 @07:41AM
(#12513310)
Why would you want to multiply by 1 or sum zero? You probably wouldn't need to do it, but computers and scripts aren't so smart as people and always follow code literally. For them is important a language having less irregularities and exceptional rules. If "" is a valid command and you have the syntax "time [COMMAND];", why not allow "time;"?
Re:Bash 4.4 released
by sillysaurus3 on Friday September 16, 2016 @07:45AM
(#12513328)
It might be to avoid errors for scripts like:
time ${cmd}; foo
where cmd happens to be unset. Conceptually, that's a valid script, because `time` standalone is a valid script. No reason it should generate an error.Not always the case, I just tried and:
$ time
real 0m0.002s user 0m0.000s sys 0m0.000s
Uh, what? Could someone explain this one, please?