On 02/27/2016 10:10 PM, Alan W. Irwin wrote:
> On 2016-02-27 23:22- Phil Rosenberg wrote:
>
>> Perhaps it would be good for Hazen and Alan to start looking
> in more detail at implementing the error code propagation? If there
> are tools to help with that, then maybe it will be easier than I
On 2016-02-27 23:22- Phil Rosenberg wrote:
> I do agree that memory allocations should not cause exits.
[...]
A failure of a single very large allocation does not always imply
the OS is in crisis.
I now agree.
> Yes I'm happy to start putting an exception based error propagation
together.
T
Hi Alan, Hazen and anyone else interested.
I do agree that memory allocations should not cause exits. I think these cases
might be less rare than you think Alan. I work with some very large datasets
and have hit memory allocation failures moderately often, although maybe that
was more when I wa
To Hazen and Phil:
Here is important additional information concerning the return code
method of implementing an error report system that should make that
method very much easier to maintain and test.
Phil originally expressed concern about the amount of developer time
it would take to implement
Hi Chris:
For a bit of background information for my response to your comment
below note that my counts show that 62 per cent of current plexit
calls are associated with memory allocation errors, but I believe that
fraction will quickly exceed 90 per cent once we become rigourous
about checking fo
On 2/24/2016 15:34, Alan W. Irwin wrote:
> On 2016-02-24 06:52-0500 Hazen Babcock wrote:
>
> [Alan]
>>> Anyhow, I am convinced by my above estimate that the propagation part
>>> of the work will require similar effort to the rest of the project, I
>>> do like the simplicity of the return code metho
