git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Completion of error handling

From
MEMarkus Elfring <markus.elfring@web.de>
Date
Feb 11, 2010, 13:08 UTC
Message-ID
<4B740153.4010600@web.de>
In-Reply-To
<alpine.LFD.2.00.1002021324290.1681@xanadu.home>
>
> What is the likelihood for those function calls to actually fail?
>

How do you think about the usual design choices that are described in the article "Exception Handling Alternatives" by Detlef Vollmann. http://accu.org/index.php/journals/546

I propose to write pointcuts for all functions that can return values. Some corresponding error codes are checked already. But there a places in the source files with open issues for complete software robustness.

Are there any chances to encapsulate more cross-cutting concerns as reusable aspects?

Would you like to integrate tools like the following into your software
development process?
- AspectC++
  http://aspectc.org/
- ACC
 
http://research.msrg.utoronto.ca/ACC/Tutorial#A_Reusable_Aspect_for_Memory_All
- Coccinelle
  http://coccinelle.lip6.fr/

Regards, Markus

Previous: Markus ElfringNext: Andreas Ericsson
Message 12 of 14 in “Completion of error handling”
  1. Markus ElfringFeb 2, 2010
  2. Nicolas PitreFeb 2, 2010
  3. Markus ElfringFeb 2, 2010
  4. Nicolas PitreFeb 2, 2010
  5. Markus ElfringFeb 2, 2010
  6. Avery PennarunFeb 2, 2010
  7. Markus ElfringFeb 2, 2010
  8. Avery PennarunFeb 2, 2010
  9. Markus ElfringFeb 2, 2010
  10. Avery PennarunFeb 2, 2010
  11. Markus ElfringFeb 2, 2010
  12. Markus ElfringFeb 11, 2010
  13. Andreas EricssonFeb 16, 2010
  14. Markus ElfringFeb 18, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.