StubClock should probably be FakeClock

[GoogleCodeExporter]

See e.g. http://martinfowler.com/articles/mocksArentStubs.html.  A "stub" is 
normally a pre-programmed implementation that contains no logic or expectations 
(q.v. EasyMock's asStubReturn()), while a "fake" is a better name for something 
that uses a non-production implementation for tests.

As it stands, I suppose that you could argue that StubClock is a stub, in that 
we currently only program it with the current time, but if we were to add any 
additional logic (e.g. as in issue 72), it's no longer an appropriate name.

Original issue reported on code.google.com by malcolm.rowe on 21 Apr 2012 at 9:36

[GoogleCodeExporter]

Blocking if we do it at all.

Original comment by malcolm.rowe on 23 Apr 2012 at 9:50

• Added labels: V1-Blocker

[GoogleCodeExporter]

Done in change d8f9a1bdb580.

Original comment by jonathan.skeet on 28 Jun 2012 at 9:19

[GoogleCodeExporter]

Original comment by jonathan.skeet on 28 Jun 2012 at 9:30

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by malcolm.rowe on 30 Jul 2012 at 7:26

• Added labels: Milestone-1.0
• Removed labels: V1-Blocker

[GoogleCodeExporter]

Original comment by malcolm.rowe on 10 Nov 2012 at 10:20

• Added labels: Milestone-1.0.0
• Removed labels: Milestone-1.0