Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!MITRE.ARPA!treid
From: treid@MITRE.ARPA (Thomas Reid)
Newsgroups: net.lang.mod2
Subject: Re: Bit stripping
Message-ID: <8608050256.AA17597@mitre.ARPA>
Date: Mon, 4-Aug-86 22:56:50 EDT
Article-I.D.: mitre.8608050256.AA17597
Posted: Mon Aug  4 22:56:50 1986
Date-Received: Tue, 5-Aug-86 23:20:02 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The MITRE Corp., Washington, D.C.
Lines: 10

I mad thought to add to the bit stripping problem (nee, opportunity).
The subject of machine dependence arose - a solution?:  Put each possible
machine interpretation in a case statement in a procedure in a module.
Then use the initialization section of the module to test which of the
possible cases are present for this execution and set the proper case
selector (of course, a static variable inside the module).  Overhead?
The initialization is executed only once, so basically just the overhead
of the case - order the case in order of likelihood and might be small.

A clever idea what?  Have the initialization test for machine dependence