https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112015-01-22T01:39:34ZRuby Issue Tracking SystemRuby master - Bug #10767: Time.local doesn't raise an exception during the dead hour on DSThttps://bugs.ruby-lang.org/issues/10767?journal_id=511662015-01-22T01:39:34Zakr (Akira Tanaka)akr@fsij.org
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-6 priority-4 priority-default closed" href="/issues/10588">Bug #10588</a>: Invalid Dates</i> added</li></ul> Ruby master - Bug #10767: Time.local doesn't raise an exception during the dead hour on DSThttps://bugs.ruby-lang.org/issues/10767?journal_id=511682015-01-22T01:49:36Zakr (Akira Tanaka)akr@fsij.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Rejected</i></li></ul><p>Sometimes an application needs a time object near the given arguments even if the time object doesn't represent the arguments exactly.<br>
It is especially useful for DST and leap second because an application cannot expect DST and leap second (unless the application contains complete timezone database).<br>
Your proposal makes the methods useless for this needs.</p>
<p>If an application want to test the argument represent a time which is not exist, it can compare obtained time object and the arguments.</p>
<p>So this proposal makes methods less useful.</p>
<p>Actually, I tried the round trip test once.<br>
(ruby-core:14517, ruby-dev:33058, r14765, r15203)<br>
But it caused troubles than benefits.</p> Ruby master - Bug #10767: Time.local doesn't raise an exception during the dead hour on DSThttps://bugs.ruby-lang.org/issues/10767?journal_id=511692015-01-22T02:37:50Zakr (Akira Tanaka)akr@fsij.org
<ul><li><strong>Assignee</strong> set to <i>akr (Akira Tanaka)</i></li></ul>