>
>
>>In Unix, an uninitialized pointer might, conceivably, scribble over
>>memory owned by the current application. But it's much more likely to
>>cause a bus error or segmentation fault. In Windows, as I understand
>>the argument, an unintialized pointer might scribble over memory owned
>>by another application, or by the OS.
>>
>>
>>
>What? "Excretum bovis", as the Romans used to say. Windows has quite as
>much memory protection as Unix, at least for 32-bit apps.
>
>
>
AFAIK, Mac OS 9 & below is the only OS that Subversion supports/will
support that allows applications to scribble on its own memory.
From here http://www.computeruser.com/articles/1910,5,18,1,1001,00.html
"*Protected memory - *We Mac users like to boast that our systems don't
crash as often as Windows. And (ahem) that's true, but they do
occasionally crash. And when one application goes down, your whole
system can go down in flames alongside it. That's because the current
Mac OS doesn't have protected memory. Mac OS X will."
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 7 16:07:53 2003