From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <2aafa5b5837f18127f5241514930f964@coraid.com> From: erik quanstrom Date: Tue, 4 Sep 2007 10:44:06 -0400 To: 9fans@cse.psu.edu Subject: Re: [9fans] plan 9 overcommits memory? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: b79120a2-ead2-11e9-9d60-3106f5b1d025 > that's a slightly different aspect. the note should not be "page fault" but > "out of memory" (or some such thing). that's much better than a nil return. > most errors on shared resoruces are better expressed as exceptions (notes), > because that's what they are: they are a failure of the underlying physical or virtual machine > to handle an exceptional case. the code shouldn't have to deal with it explicitly everywhere, > except in C to detect and propagate the exception to code that knows what's going on. if one wishes to be remotely standards-compliant, sending a note on allocation failure is not an option. k&r 2nd ed. p. 252. - erik