| | A More Seamless Checking Wrapper for Raw C++ Pointers (Site not responding. Last check: 2007-10-12) |
 | | The "original" checked pointers component for C++ [Pike00] did a very good job of detecting many precondition violations for raw C++ pointers, including dereferencing a NULL or dangling pointer and deleting a dangling pointer. |
 | | Checked pointers are implemented by two separate components: Pointer, a template which is directly used by the client programmer, and Pointer_Map, a class which underlies Pointer, and is the workhorse for detecting pointer violations (e.g., deletion of dangling pointers). |
 | | If you take the view that raw pointers in C++ are a service providing component, then it follows that there should be a checked version of raw C++ pointers, and that this checked version should be used during the development phase of any client that relies on raw C++ pointers. |
| people.cs.vt.edu /~edwards/RESOLVE2002/proceedings/Hollingsworth1.html (2770 words) |