Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rochester!ur-tut!sunybcs!rutgers!labrea!decwrl!pyramid!voder!blia!forrest
From: forrest@blia.BLI.COM (Jon Forrest)
Newsgroups: comp.os.vms
Subject: Re: Are Transfer Vectors Truly Useful W
Message-ID: <2977@blia.BLI.COM>
Date: Mon, 20-Jul-87 16:55:47 EDT
Article-I.D.: blia.2977
Posted: Mon Jul 20 16:55:47 1987
Date-Received: Wed, 22-Jul-87 04:28:46 EDT
References: <2961@blia.BLI.COM> <46200001@ccvaxa>
Organization: Britton Lee, Berkeley, CA
Lines: 24

In article <46200001@ccvaxa>, aglew@ccvaxa.UUCP writes:
> 
> 
> The solution is really simple. Have a section of code that will
> always be at a fixed address and will contain pointers to the data structures.
> The pointers will always be 4 bytes and the addresses won't change. You
> can change the size of the structure and you could even change it 
> at run time and the program won't care since it always accesses it through
> the pointer that is in a known location. 

As I said in my original posting this kind of solution wasn't what
I had in mind mainly because the code has to be portable. To implement
this solution I'll have to convince a bunch of people to change some
non-trivial code. It is a good idea, though, since it's just the same
thing as transfer vectors.

Any other comments or suggestions?


Jon Forrest

forrest@blia.BLI.COM
ucbvax!mtxinu!blia!forrest
{pyramid|voder}!blia!forrest