6502/llvm-6502
1
0
Fork 0
mirror of https://github.com/c64scene-ar/llvm-6502.git synced 2024-10-02 02:55:35 +00:00
Code Issues Projects Releases Wiki Activity

we beat exceptions out of lib/system a long time ago.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@76240 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Chris Lattner 2009-07-17 21:11:24 +00:00
parent 0768f0eb7f
commit 3ddd717f17
1 changed files with 4 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
docs/SystemLibrary.html
View File

@ -23,7 +23,6 @@
<li><a href="#nounused">No Unused Functionality</a></li>
<li><a href="#virtuals">No Virtual Methods</a></li>
<li><a href="#softerrors">Minimize Soft Errors</a></li>
<li><a href="#throw">Throw Only std::string</a></li>
<li><a href="#throw_spec">No throw() Specifications</a></li>
<li><a href="#organization">Code Organization</a></li>
<li><a href="#semantics">Consistent Semantics</a></li>
@ -211,8 +210,8 @@
"out of space", "bad disk sector", or "system call interrupted". We'll call
the first group "<i>soft</i>" errors and the second group "<i>hard</i>"
errors.<p>
<p>lib/System must always attempt to minimize soft errors and always just
throw a std::string on hard errors. This is a design requirement because the
<p>lib/System must always attempt to minimize soft errors.
This is a design requirement because the
minimization of soft errors can affect the granularity and the nature of the
interface. In general, if you find that you're wanting to throw soft errors,
you must review the granularity of the interface because it is likely you're
@ -239,31 +238,6 @@
</ol>
</div>
<!-- ======================================================================= -->
<div class="doc_subsection"><a name="throw">Throw Only std::string</a></div>
<div class="doc_text">
<p>If an error occurs that lib/System cannot handle, the only action taken by
lib/System is to throw an instance of std:string. The contents of the string
must explain both what happened and the context in which it happened. The
format of the string should be a (possibly empty) list of contexts each
terminated with a : and a space, followed by the error message, optionally
followed by a reason, and optionally followed by a suggestion.</p>
<p>For example, failure to open a file named "foo" could result in a message
like:</p>
<ul><li>foo: Unable to open file because it doesn't exist."</li></ul>
<p>The "foo:" part is the context. The "Unable to open file" part is the error
message. The "because it doesn't exist." part is the reason. This message has
no suggestion. Where possible, the implementation of lib/System should use
operating system specific facilities for converting the error code returned by
a system call into an error message. This will help to make the error message
more familiar to users of that type of operating system.</p>
<p>Note that this requirement precludes the throwing of any other exceptions.
For example, various C++ standard library functions can cause exceptions to be
thrown (e.g. out of memory situation). In all cases, if there is a possibility
that non-string exceptions could be thrown, the lib/System library must ensure
that the exceptions are translated to std::string form.</p>
</div>
<!-- ======================================================================= -->
<div class="doc_subsection"><a name="throw_spec">No throw Specifications</a>
</div>
@ -273,7 +247,8 @@
compiler does not insert additional exception handling code into the interface
functions. This is a performance consideration: lib/System functions are at
the bottom of many call chains and as such can be frequently called. We
need them to be as efficient as possible.</p>
need them to be as efficient as possible. However, no routines in the
system library should actually throw exceptions.</p>
</div>
<!-- ======================================================================= -->