From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: a07f3367d7,5b528da331e8df66
X-Google-Attributes: gida07f3367d7,public,usenet
X-Google-NewGroupId: yes
X-Google-Language: ENGLISH,ASCII-7-bit
X-Received: by 10.180.188.52 with SMTP id fx20mr788644wic.3.1365267391837;
        Sat, 06 Apr 2013 09:56:31 -0700 (PDT)
Path: 
 ex12ni26833wid.1!nntp.google.com!feeder1.cambriumusenet.nl!82.197.223.108.MISMATCH!feeder2.cambriumusenet.nl!feed.tweaknews.nl!85.12.40.131.MISMATCH!xlned.com!feeder3.xlned.com!198.15.118.135.MISMATCH!us.feeder.erje.net!1.eu.reader.erje.net!feeder.erje.net!eu.feeder.erje.net!eternal-september.org!feeder.eternal-september.org!mx05.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Marble Clock
Date: Wed, 03 Apr 2013 10:14:07 +0100
Organization: A noiseless patient Spider
Message-ID: <lyobdwgen4.fsf@pushface.org>
References: <7075541f-01b7-4cd4-997f-b0b8048f067d@googlegroups.com>
	<nospam-24C17F.08024402042013@news.aioe.org>
	<e20eda83-2320-48ca-83da-b13d7df3dc1c@googlegroups.com>
	<b3a57b60-3f54-4be7-ae4a-364914b8b827@googlegroups.com>
Mime-Version: 1.0
Injection-Info: mx05.eternal-september.org;
 posting-host="72a7bb6120f61bc7749e29c9c2e535af";
	logging-data="19206"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX18atNQSk8J0RrkvG6pf7Y7WZq2Prxw4pJE="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (darwin)
Cancel-Lock: sha1:d9n6Tsh2cIik5JB0+JVh/XIEOuc=
	sha1:7GMDblZHU4itsxNAdn5nEGRptfw=
Content-Type: text/plain
Date: 2013-04-03T10:14:07+01:00
List-Id: <comp.lang.ada>

Eryndlia Mavourneen <eryndlia@gmail.com> writes:

> On Tuesday, April 2, 2013 2:46:10 PM UTC-5, gattamaneni abhiram wrote:

>> Do I need to use timer functions in the program to depict the changes
>> in the places of the marbles in different trays?
>
> I believe that would be the simpler way to do it.  Of course, you
> always can simulate the materials and workmanship of an actual clock
> with masses, gravitational acceleration, etc.  :-)
>
> Note that the non-realtime timer in Ada is the "delay" statement:
> "delay 3.1", for example, will delay for 3.1 seconds.

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.

IRL there will be a finite delay for the mechanism to click through any
carries that may be needed, but I very much doubt you're required to
simulate that.


BTW, people, did you notice how I trimmed the quoted part of this so
that it only contains the bit I'm actually replying to? You seem to be
Google Groups users, so you probably don't notice what a complete pig's
ear GG makes of quoting!!!