Question 1

How do I clean up memory when using CException?

Accepted Answer

CException does not automatically free memory. You must explicitly call free() or other cleanup functions in the Catch block after an exception is thrown to prevent memory leaks, as noted in the limitations section.

Question 2

CException vs traditional error codes - which is better for C?

Accepted Answer

CException offers cleaner syntax and reduces error propagation boilerplate across function calls, but error codes might be simpler for very small projects or when you need immediate handling without setjmp/longjmp overhead.

Question 3

Can CException be used in multi-threaded applications?

Accepted Answer

Yes, but it requires configuration with unique task IDs for each thread. Define CEXCEPTION_GET_ID to return thread IDs and CEXCEPTION_NUM_ID for the thread count, as explained in the multitasking support section.

Question 4

How to set up CException for FreeRTOS?

Accepted Answer

Define CEXCEPTION_GET_ID to call a function that returns the FreeRTOS task ID, and set CEXCEPTION_NUM_ID to the maximum number of tasks. Include FreeRTOS headers in your configuration for seamless integration.

Question 5

Is CException thread-safe?

Accepted Answer

It can be made thread-safe with proper configuration for multitasking, but you must ensure that task IDs are unique and consistent. The library itself doesn't handle thread synchronization, so additional care is needed in concurrent environments.

Question 6

How to rethrow an exception in CException?

Accepted Answer

Inside a Catch block, call Throw(e) with the caught exception ID to rethrow it to an outer Try block. This allows for nested error handling, as mentioned in the API documentation.

CException

What is CException?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions