Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!umd5!mimsy!oddjob!gargoyle!att!ihnp4!poseidon!ech
From: ech@poseidon.UUCP (Edward C Horvath)
Newsgroups: comp.sys.mac.programmer
Subject: Re: A few questions about Ticks
Message-ID: <460@poseidon.UUCP>
Date: 28 Jul 88 18:58:57 GMT
References: <3417@polya.Stanford.EDU>
Organization: AT&T Information Systems, Lincroft, NJ
Lines: 10

> 2)  Why use the TickCount() trap when the Global variable Ticks is available?
> 	I realize that the underlying philosophy is that it makes future
> 	compatibility more likely, but it seems to me that Ticks is a machine
> 	state, not a process state...

But it's just a copy of a real timer elsewhere.  Under A/UX, or any future Mac
OS that memory-maps the low-memory globals, the TickCount trap can be
supported by checking the hardware clock; but keeping the Ticks global
up-to-date is fairly wastful.

=Ned Horvath=