Path: utzoo!attcan!uunet!husc6!think!ames!amdahl!nsc!voder!apple!dwb
From: dwb@Apple.COM (David W. Berry)
Newsgroups: comp.sys.mac.programmer
Subject: Re: A few questions about Ticks
Message-ID: <14799@apple.Apple.COM>
Date: 27 Jul 88 18:58:55 GMT
References: <3417@polya.Stanford.EDU>
Reply-To: dwb@apple.apple.com.UUCP (David W. Berry)
Organization: Apple Computer Inc, Cupertino, CA
Lines: 24

In article <3417@polya.Stanford.EDU> rothberg@polya.Stanford.EDU (Edward Rothberg) writes:
>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, and therefore there doesn't seem to be
>	a great motivation to get rid of it.  Is it in Apple's list of
>	"targeted" low-memory globals, globals that Apple says will have to
>	go in the future?
	Well, for one thing, A/UX only supports Ticks with pain and suffering
to the user, ie. it slows down the whole machine.  The default setup is that
it isn't supported.  This may very well be true of other future Apple OS's
that support memory protection.
>
>Ed Rothberg
>rothberg@polya.stanford.edu




Opinions:  MINE, ALL MINE! (greedy evil chuckle)

David W. Berry
apple!dwb@sun.com	dwb@apple.com	973-5168@408.MaBell