From: Markus Elfring <Markus.Elfring@web.de>
To: Nicolas Pitre <nico@fluxnic.net>
Cc: git@vger.kernel.org
Subject: Re: Completion of error handling
Date: Thu, 11 Feb 2010 14:08:35 +0100 [thread overview]
Message-ID: <4B740153.4010600@web.de> (raw)
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
next prev parent reply other threads:[~2010-02-11 13:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 13:11 Completion of error handling Markus Elfring
2010-02-02 18:26 ` Nicolas Pitre
2010-02-02 18:49 ` Markus Elfring
2010-02-02 19:27 ` Nicolas Pitre
2010-02-02 19:42 ` Markus Elfring
2010-02-02 19:49 ` Avery Pennarun
2010-02-02 20:10 ` Markus Elfring
2010-02-02 20:25 ` Avery Pennarun
2010-02-02 21:26 ` Markus Elfring
2010-02-02 21:27 ` Avery Pennarun
2010-02-02 21:55 ` Markus Elfring
2010-02-11 13:08 ` Markus Elfring [this message]
2010-02-16 10:56 ` Andreas Ericsson
2010-02-18 15:11 ` Markus Elfring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B740153.4010600@web.de \
--to=markus.elfring@web.de \
--cc=git@vger.kernel.org \
--cc=nico@fluxnic.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).