home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!uknet!doc.ic.ac.uk!agate!spool.mu.edu!uwm.edu!cs.utexas.edu!rutgers!cmcl2!acf3!silbrmnd
- From: silbrmnd@acf3.nyu.edu (Darkmage)
- Newsgroups: comp.ai.philosophy
- Subject: Re: The Humongous Look-up Table revisited.
- Message-ID: <BzxM8E.7Et@cmcl2.nyu.edu>
- Date: 27 Dec 92 19:02:38 GMT
- References: <1992Dec22.211814.5623@u.washington.edu> <1992Dec23.174604.9946@sophia.smith.edu> <Bzst9t.79B@cmcl2.nyu.edu> <1992Dec26.132916.7342@sophia.smith.edu>
- Sender: notes@cmcl2.nyu.edu (Notes Person)
- Organization: New York University
- Lines: 13
- Nntp-Posting-Host: acf3.nyu.edu
-
- orourke@sophia.smith.edu (Joseph O'Rourke) writes:
-
- >In article <Bzst9t.79B@cmcl2.nyu.edu> silbrmnd@acf3.nyu.edu (Darkmage) writes:
-
- >> Q: What time do you think it is in Seattle right now?
- >> A: Uh... I think it's around {TIME_NOW - 5 HOUR /Hour Only} -ish.
-
- > It ceases to be a lookup table if such hooks into the contextual
- >reality are permitted.
-
- If the machine in question has a built-in clock, the entry in the table
- would just be telling it to "insert time here"; all it's doing is
- looking something up somewhere else.
-