Completion of error handling

[elfring]

Would you like to add more error handling for return values from functions like the following?

• malloc ⇒ vkvg_create
• realloc ⇒ _increase_font_tex_array

[jpbruyere]

I've not yet implemented any exception handling, but if you have a clear idea of what you want, feel free to submit a pull request.

[elfring]

I suggest to avoid ignorance of return values a bit more.
Would you like to detect every error situation as early as possible?

[jpbruyere]

You are right that error handling is a key part, but I feel more comfortable with the idea of implementing a single error handling pattern as a whole in a dedicated step of the development. I guess the advantage is to keep the code as simple (and readable) as possible in the early steps of creation. And as long as the software is run in a debug environment, error handling isn't critical. It is even sometimes harder to debug with errors routed to the top of the library. But any idea and help is welcome.

[elfring]

How do you think about to improve static source code analysis also for this software?

---

• Are you interested to apply aspect-oriented software development?
• Would you like to encapsulate error detection and corresponding exception handling as a reusable aspect in your software?

[jpbruyere]

Static source code analyzers are handy tools, but using them too early could limit creativity and intuition. Also being rigorous by yourself instead of being driven by a soft is a must. Letting a software making lots of tiny changes in your draft could have bad consequence.
For error handling, I will try to make them non-blocking where possible, but producing a reusable aspect is not really in my plans.

[elfring]

Can higher level development tools help to improve also this software implementation further?

[jpbruyere]

You think to a particular tool?

[elfring]

Yes. - There are development tools available which could help more with the desired completion of exception handling.
🔮 How do you think about to extend the software tool box?

[jpbruyere]

tell me more...which soft?

[elfring]

Examples:

• Programming language “C++”
• Semantic patch language (Coccinelle)
• AspectC++

[jpbruyere]

If you have good experience with those tools, I'm open to any pull request that could improve vkvg.

[elfring]

I know these tools to some degree.
🔮 How will their application acceptance evolve by other software designers, system testers and developers?

[elfring]

• How do you think about to work with functions which can throw C++ exceptions?
• Would you like to integrate the tool “AspectC++” into your software build process?

[jpbruyere]

No, vkvg is a c library.

[elfring]

Can functions of a C library call (member) functions of a class library for this software?