From: Simon Wright <simon@pushface.org>
Subject: Re: Marble Clock
Date: Wed, 03 Apr 2013 17:53:31 +0100
Date: 2013-04-03T17:53:31+01:00 [thread overview]
Message-ID: <lyk3ojh7xw.fsf@pushface.org> (raw)
In-Reply-To: lyobdwgen4.fsf@pushface.org
Simon Wright <simon@pushface.org> writes:
> You (gattameini) definitely should *not* use more than one timer
> function (when_to_run := when_to_run + 1.0; delay until when_to_run;),
> for when the next marble is to enter the top tray.
Sorry, I've just re-read the question: that should be 60.0 seconds, not
1.0!
The point I was trying & probably failing to make is that 'delay 60.0'
results in a delay of _at least_ 60 seconds, which would make your clock
run slow. This is rather an advanced point, probably not relevant to
your exercise.
next prev parent reply other threads:[~2013-04-03 16:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 0:09 Marble Clock gattamaneni abhiram
2013-04-02 12:02 ` John B. Matthews
2013-04-02 19:46 ` gattamaneni abhiram
2013-04-02 19:54 ` Eryndlia Mavourneen
2013-04-03 9:14 ` Simon Wright
2013-04-03 12:45 ` Eryndlia Mavourneen
2013-04-03 16:53 ` Simon Wright [this message]
2013-04-12 22:28 ` gattamaneni abhiram
2013-04-13 5:51 ` Simon Wright
2013-04-13 19:04 ` Dennis Lee Bieber
2013-04-03 11:52 ` John B. Matthews
2013-04-03 7:44 ` Mike H
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox