|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| D.B. Lomet, "Making Pointers Safe in System Programming Languages," IEEE Transactions on Software Engineering, vol. 11, no. 1, pp. 87-96, January, 1985. | |||
| BibTex | x | ||
| @article{ 10.1109/TSE.1985.231846, author = {D.B. Lomet}, title = {Making Pointers Safe in System Programming Languages}, journal ={IEEE Transactions on Software Engineering}, volume = {11}, number = {1}, issn = {0098-5589}, year = {1985}, pages = {87-96}, doi = {http://doi.ieeecomputersociety.org/10.1109/TSE.1985.231846}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - JOUR JO - IEEE Transactions on Software Engineering TI - Making Pointers Safe in System Programming Languages IS - 1 SN - 0098-5589 SP87 EP96 EPD - 87-96 A1 - D.B. Lomet, PY - 1985 KW - safety KW - Efficiency KW - pointers KW - programming languages VL - 11 JA - IEEE Transactions on Software Engineering ER - | |||
System programming languages usually provide pointers so as to permit efficient and understandable programs to be written. Some higher level languages either avoid pointers altogether or greatly circumscribe pointers to guarantee safety, i.e., so that programs cannot gain access to storage in an inappropriate way. By combining the ideas of 1) pointer scope front Algol 68, 2) tombstones for invalidating dangling references, and 3) freezing which permits freeable objects to have scoped pointers, we solVe the problem of providing convenient and efficient pointers while simultaneously guaranteeing safety.
Index Terms:
safety, Efficiency, pointers, programming languages
Citation:
D.B. Lomet, "Making Pointers Safe in System Programming Languages," IEEE Transactions on Software Engineering, vol. 11, no. 1, pp. 87-96, Jan. 1985, doi:10.1109/TSE.1985.231846
Usage of this product signifies your acceptance of the Terms of Use.

