Den Wed, 29 Aug 2018 10:00:34 +0100 skrev smf <smf@null.net>: > On 28/08/2018 14:01, Julian Perry wrote: > > I found it incomprehensible then (as I do now) why an allocated > > buffer from a seek command that returned "Drive not ready" was not > > able to be stolen / returned to the free pool, particularly as in > > most instances the buffer allocated had no file-handle associated > > with it (being from a failed intialisation predicating a directory > > listing) > > A couple of guesses spring to mind. > > 1. Left over debugging code, when an error occurs then being able to > look at the buffer would be quite useful. It was either left in by > accident, or because changing it was deemed too dangerous. > > 2. A workround for another bug which may have been fixed & the > workround left in, or it might be less serious than save@ and nobody > noticed. 3. Maybe you are always supposed to deallocate a buffer when done? -- (\_/) Copy the bunny to your mails to help (O.o) him achieve world domination. (> <) Come join the dark side. /_|_\ We have cookies.Received on 2018-08-29 14:00:05
Archive generated by hypermail 2.2.0.