Closed GoogleCodeExporter closed 9 years ago
The things you propose definitely should be implemented in some way. I'll think
more about it and implement in the next release.
Original comment by zexspect...@gmail.com
on 28 Sep 2011 at 2:44
Issue 108 has been merged into this issue.
Original comment by zexspect...@gmail.com
on 9 Oct 2011 at 3:48
I decided to introduce new flag CR_INST_ALL_POSSIBLE_HANDLERS (0x1FFF) and make
the old flag CR_INST_ALL_EXCEPTION_HANDLERS (0) deprecated:
#define CR_INST_ALL_POSSIBLE_HANDLERS 0x1FFF //!< Install all
possible exception handlers.
#define CR_INST_ALL_EXCEPTION_HANDLERS 0 //!< Deprecated, not
recommended to use. Use \ref CR_INST_ALL_POSSIBLE_HANDLERS instead.
I understand your idea with CR_INST_NO_EXCEPTION_HANDLERS flag, but this is not
100% clean solution. Assume you need to install thread exception handlers only.
But crInstall is designed to install thread-based exception handlers for the
main thread, you can't install thread-based exception handlers for the main
thread with crInstallToCurrentThread2(). So, you have to provide some
handler-related flags for crInstall() function. Finally, I decided not to
introduce the CR_INST_NO_EXCEPTION_HANDLERS flag becouse of the reason above.
Original comment by zexspect...@gmail.com
on 9 Oct 2011 at 4:12
Fixed in v.1.3.0
Original comment by zexspect...@gmail.com
on 22 Oct 2011 at 11:07
Original issue reported on code.google.com by
Schoenle...@googlemail.com
on 20 Sep 2011 at 8:34