commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Horst Gernhardt (JIRA)" <j...@apache.org>
Subject [jira] Created: (LANG-315) StopWatch: suspend() acts as split(), if followed by stop()
Date Tue, 06 Feb 2007 13:53:05 GMT
StopWatch: suspend() acts as split(), if followed by stop()
-----------------------------------------------------------

                 Key: LANG-315
                 URL: https://issues.apache.org/jira/browse/LANG-315
             Project: Commons Lang
          Issue Type: Bug
    Affects Versions: 2.2, 2.1, 2.0
            Reporter: Horst Gernhardt


In my opinion, it is a bug that suspend() acts as split(), if followed by stop(); see below:

        StopWatch sw = new StopWatch();

        sw.start();
        Thread.sleep(1000);
        sw.suspend();
        // Time 1 (ok)
        System.out.println(sw.getTime());

        Thread.sleep(2000);
        // Time 1 (again, ok)
        System.out.println(sw.getTime());

        sw.resume();
        Thread.sleep(3000);
        sw.suspend();
        // Time 2 (ok)
        System.out.println(sw.getTime());

        Thread.sleep(4000);
        // Time 2 (again, ok)
        System.out.println(sw.getTime());

        Thread.sleep(5000);
        sw.stop();
        // Time 2 (should be, but is Time 3 => NOT ok)
        System.out.println(sw.getTime());


suspend/resume is like a pause, where time counter doesn't continue. So a following stop()-call
shouldn't increase the time counter, should it?


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message