I was just kidding!
Dan Adams wrote:
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 w
Robin,
There a number of issues involved with considering moving to
try/throw/catch error handling. The first one that comes to mind is
language binding. Second is cross-platform portability with OSs like
PocketPC, which, if I remember correctly don't have compilers that
support exceptions
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
t
[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
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 fro
It has been a long time since I have coded in C++ but I seem to remember
that a program can set a global memory error handler. Then this error
can do something marginally appropriate for the problem. In our
situation, we used it to try to log a short static message and exit the
program.
When
On 10/06/05, Troy A. Griffitts <[EMAIL PROTECTED]> wrote:
> 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
> proble
On Friday 10 June 2005 12:04, Daniel Glassey wrote:
> On 07/06/05, Mark Dayton <[EMAIL PROTECTED]> wrote:
> > Is any effort being made to update QPSword?
> >
> > Thanks,
> >
> > Mark
>
> Hi Mark,
> I don't know of any efforts on QPSword but I know there is a program
> called opie dagger that is par
Greg,
OSIS' purpose is to mark the elements in a text as what they are, not
how they should be displayed. The way elements are displayed is left
out for another 'presentation layer' to handle as it sees fit.
Now, having said that, there is an evil workaround for elements that
you just can'
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 th
Hi,
While encountering other problems on my machine I've found a potential
problem with SWBuf::assureSize.
It reallocs or mallocs the buffer but doesn't check that that has
succeeded before setting the 'end' of the buffer to 0.
Patch attached that does a check. Thought I'd just check before check
On 07/06/05, Mark Dayton <[EMAIL PROTECTED]> wrote:
> Is any effort being made to update QPSword?
>
> Thanks,
>
> Mark
Hi Mark,
I don't know of any efforts on QPSword but I know there is a program
called opie dagger that is part of the latest release of opie. Though
I don't know if it is being a
Here is a starting thought on the format of the osis.
I took three simple cases:
The first is about as simple as they come, but has several Bible references.
The second adds an internal cross reference.
The third has several definitions.
First the original from hard copy: (I point out the hard c
Hey Troy,
thank you for your hard work.
> Here is my best attempt at a beta before I leave for the summer. Give
> it a go and let me know what you think.
It showed the Bible intros in der GerNeÜ for Matthew, but not for Josua. But I
think showing it for Matthew is good enough to release t
14 matches
Mail list logo
