THE DESIGN OF THE MEMORY POOL SYSTEM SIGNATURE SYSTEM
design.mps.sig
incomplete design
richard 1995-08-25
TESTING:
.test.uniq: The unix command
sed -n '/^#define [a-zA-Z]*Sig/s/[^(]*(/(/p' *.[ch]| sort| uniq -c
will display all signatures defined in the mps along with a count of how many
times they are defined. If any counts are greater than 1, then the same
signature value is being used for different signatures. This is undesirable
and the problem should be investigated. People not using unix may still find
the RE useful.
TEXT:
Signatures are magic numbers which are written into structures
when they are created and invalidated (by overwriting with
SigInvalid) when they are destroyed. They provide a limited form
of run-time type checking and dynamic scope checking.
Signature values should be transliterations of the corresponding words into
hex, as guide.hex.trans. The first three hex digits should be the
transliteration of "SIG".
A. References
B. Document History
| 2002-06-07 | RB | Converted from MMInfo database design document. |
C. Copyright and License
This document is copyright © 1995-2002 Ravenbrook Limited. All rights reserved. This is an open source license. Contact Ravenbrook for commercial licensing options.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Redistributions in any form must be accompanied by information on how to obtain complete source code for the this software and any accompanying software that uses this software. The source code must either be included in the distribution or be available for no more than the cost of distribution plus a nominal fee, and must be freely redistributable under reasonable conditions. For an executable file, complete source code means the source code for all modules it contains. It does not include source code for modules or files that typically accompany the major components of the operating system on which the executable file runs.
This software is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement, are disclaimed. In no event shall the copyright holders and contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage.