effect of free()

[T. William Wells]

In article <11121 at smoke.BRL.MIL> gwyn at brl.arpa (Doug Gwyn) writes:
: It's not very hard to factor in the notion that a pointer is "poison"
: when it no longer points to valid storage.  One would think that
: "well-written code" would already follow that model, which is
: compatible with a wider range of environments.

Mine always did. Even before I learned to think about portability. It
just never occured to me that a freed pointer was anything but
nonsense.

---
Bill                    { uunet | novavax | ankh | sunvice } !twwells!bill
bill at twwells.com