<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1498" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><SPAN class=974341702-11062005>Yes, but writing Java code rather than c++
isn't necessarily the solution if the project is to be programmed in c++. I am
not necessarily suggesting a solution, but I am in agreement with Robin that
using the try/catch/throw stuff along with garbage collection is a good idea
through whatever programming.</SPAN></DIV>
<DIV><SPAN class=974341702-11062005></SPAN> </DIV>
<DIV><SPAN class=974341702-11062005><FONT face=Arial
size=2>Dan</FONT></SPAN></DIV>
<DIV><SPAN class=974341702-11062005></SPAN> </DIV>
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B>
sword-devel-bounces@crosswire.org [mailto:sword-devel-bounces@crosswire.org]
<B>On Behalf Of </B>DM Smith<BR><B>Sent:</B> Friday, June 10, 2005 7:04
PM<BR><B>To:</B> SWORD Developers' Collaboration Forum<BR><B>Subject:</B> Re:
[sword-devel] Re: sword-devel Digest, Vol 15, Issue 13
ErrorHandling<BR><BR></FONT></DIV><A class=moz-txt-link-abbreviated
href="mailto:RLRANDALLX@aol.com">RLRANDALLX@aol.com</A> wrote:
<BLOCKQUOTE cite=midce.6a538640.2fdb95c8@aol.com type="cite">
<META content="MSHTML 6.00.2900.2627" name=GENERATOR><FONT id=role_document
face=Arial color=#000000 size=2>
<DIV>
<DIV>
<DIV>In a message dated 6/10/2005 12:03:57 P.M. Pacific Daylight Time, <A
class=moz-txt-link-abbreviated
href="mailto:sword-devel-request@crosswire.org">sword-devel-request@crosswire.org</A>
writes:</DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: blue 2px solid"><FONT
style="BACKGROUND-COLOR: transparent" face=Arial color=#000000
size=2><BR>Hey Daniel,<BR> Thanks for the catch, but we don't
check for successful memory <BR>allocation anywhere in the engine. I'm
not sure what we'd do if we ran <BR>out of memory. Gracefully
degradating from such a state is a complex <BR>problem. Also, our
engine doesn't use try/catch/throw error handling, <BR>so throwing anything
would cross a consistency line. Note: not debating <BR>that we
SHOULDN'T use exception error handling, only that we currently <BR>do
not</FONT></BLOCKQUOTE></DIV>Troy,</DIV>
<DIV> </DIV>
<DIV>Wearing my QA hat, I think we ought to plan on using try/catch/throw
error handling pretty soon. How about after your sabbatical?:) Also can
we set some standard for garbage collection? For example when we
construct a temporary object is the deconstructor working properly to clean
things up? I'm not a C++ programmer, so maybe you have some better ideas to
help keep us from running out of memory.</DIV>
<DIV> </DIV></FONT></BLOCKQUOTE>I have found the best way to handle memory
problems in C++ is to write code in Java ;)<BR></BODY></HTML>