<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
<title></title>
</head>
<body>
<p style="margin: 0px;"><span> </span></p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px 5px 0px;">
Hans-Peter Diettrich <DrDiettrich1@aol.com> hat am 27. Juni 2011 um 16:58 geschrieben:<br/>
<br/>
> Martin schrieb:<br/>
><br/>
> > See my example about memory alloc in my other mail. It shows, that a<br/>
> > piece of code (and it's ability to be "safely invoked ") does not solely<br/>
> > depend on the parameters passed, but also on (selected parts of) the<br/>
> > state of the application or system.<br/>
><br/>
> What when some code does not return anything, *and* cannot work at all<br/>
> due to some problem (out-of-memory, file deleted, object destroyed...)?<br/>
><br/>
> When e.g. a file search cannot proceed due to missing access rights? It<br/>
> cannot return an boolean value (succ/fail), because it's simply unknown<br/>
> whether the file exists.<br/>
><br/>
> When in case of an unexpected error the called procedure throws an<br/>
> exception? Can this procedure *ever* be "safely invoked", when it may<br/>
> return to some other place in code (exception handler)?
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">Yes, if raising an IO exception is a valid output. </p>
<div style="margin: 5px 0px 5px 0px;">
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">Mattias</p>
<p style="margin: 0px;"> </p>
</body>
</html>