Hello, Andy Wingo <wi...@pobox.com> writes:
> I'm hacking on this code right now, and have come to think that > scm_array_handle_release is superfluous. It shouldn't protect against > concurrent modification of the data, as that should be done with > user-implemented mutexen. It obviously doesn't do anything now -- and > really, it doesn't have anything to do. I can't think of a /supported/ > modification of an array that will leave a pointer to the elements > invalid -- i.e. we have no truncation ops that I know of. How about copy-on-write stringbufs as produced by `substring'? I suppose it's only a problem is the stringbuf is accessed concurrently, though. Thanks, Ludo'.
