RE: [sword-devel] Re: sword-devel Digest, Vol 15, Issue 13 ErrorHandling

[Dan Adams]

Title: Message

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.   Dan   -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of DM Smith Sent: Friday, June 10, 2005 7:04 PM To: SWORD Developers' Collaboration Forum Subject: Re: [sword-devel] Re: sword-devel Digest, Vol 15, Issue 13 ErrorHandling [EMAIL PROTECTED] wrote: In a message dated 6/10/2005 12:03:57 P.M. Pacific Daylight Time, [EMAIL PROTECTED] writes: Hey Daniel,     Thanks for the catch, but we don't check for successful memory allocation anywhere in the engine.  I'm not sure what we'd do if we ran out of memory.  Gracefully degradating from such a state is a complex problem.  Also, our engine doesn't use try/catch/throw error handling, so throwing anything would cross a consistency line.  Note: not debating that we SHOULDN'T use exception error handling, only that we currently do not Troy,   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.   I have found the best way to handle memory problems in C++ is to write code in Java ;)

_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page