Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #19501
| Newsgroups | comp.lang.javascript |
|---|---|
| Subject | Re: About format to always use 2 digits for hour |
| From | "Evertjan." <exxjxw.hannivoort@inter.nl.net> |
| References | <kl60sb$9nn$1@dont-email.me> <XnsA1ABB47255529eejj99@194.109.133.133> <EU$n+pH2qEeRFwOq@invalid.uk.co.demon.merlyn.invalid> <XnsA1AD622F8E024eejj99@194.109.133.133> <$NL54QElvteRFw5D@invalid.uk.co.demon.merlyn.invalid> |
| Date | 2013-04-27 10:50 +0200 |
| Message-ID | <XnsA1AF6E3FF2DFeejj99@194.109.133.133> (permalink) |
Dr J R Stockton wrote on 26 apr 2013 in comp.lang.javascript:
> In comp.lang.javascript message <XnsA1AD622F8E024eejj99@194.109.133.133>
> , Thu, 25 Apr 2013 09:39:07, Evertjan. <exxjxw.hannivoort@inter.nl.net>
> posted:
>
>>
>>function two(x) { return !isNaN(x) && x<10 && x>=0 ?"0" + x :x }
> Gives an inappropriate string if the argument is the null value.
How could you geve an appropriate string?
> The slicing methods are acceptable for in-range inputs, or if the input
> may be larger but only the last two digits are wanted.
>
> But consider two(D.getMilliseconds()) ; that will give the last two
> digits, and the output will always look correct. But if there has been
> an editing mistake, converting a tested D.getSeconds() into
> D.getMilliseconds(), the output of your function two will still always
> look plausible, whereas that of my function LZ will, nine times out of
> ten, show three digits - and that will ease detection of the *real*
> error. Etc.
Good reasoning.
However, in this forum, I prefer educational symplicity to detection of
programmatical errors.
>>.. both loosing the educational symplicity of:
>
> YSCIB.
Eye yous noh essie.
--
Evertjan.
The Netherlands.
(Please change the x'es to dots in my emailaddress)
Back to comp.lang.javascript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
About format to always use 2 digits for hour "Tony" <tony.johansson@inport.com> - 2013-04-23 15:07 +0200
Re: About format to always use 2 digits for hour JJ <duh@nah.meh> - 2013-04-23 20:55 +0700
Re: About format to always use 2 digits for hour "Jukka K. Korpela" <jkorpela@cs.tut.fi> - 2013-04-23 16:58 +0300
Re: About format to always use 2 digits for hour "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-04-23 17:44 +0200
Re: About format to always use 2 digits for hour "Mel Smith" <med_cutout_syntel@aol.com> - 2013-04-23 12:40 -0600
Re: About format to always use 2 digits for hour Christoph Becker <cmbecker69@gmx.de> - 2013-04-23 21:02 +0200
Re: About format to always use 2 digits for hour Dr J R Stockton <reply1300@merlyn.demon.co.uk.invalid> - 2013-04-24 22:12 +0100
Re: About format to always use 2 digits for hour "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-04-25 09:39 +0200
Re: About format to always use 2 digits for hour Dr J R Stockton <reply1300@merlyn.demon.co.uk.invalid> - 2013-04-26 20:56 +0100
Re: About format to always use 2 digits for hour "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-04-27 10:50 +0200
Re: About format to always use 2 digits for hour Dr J R Stockton <reply1300@merlyn.demon.co.uk.invalid> - 2013-04-28 16:49 +0100
Re: About format to always use 2 digits for hour Stefan Weiss <krewecherl@gmail.com> - 2013-04-29 01:19 +0200
Re: About format to always use 2 digits for hour "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2013-04-29 09:05 +0200
Re: About format to always use 2 digits for hour Dr J R Stockton <reply1300@merlyn.demon.co.uk.invalid> - 2013-04-30 22:14 +0100
csiph-web