git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Nicolas Pitre <nico@fluxnic.net>, git@vger.kernel.org
Subject: Re: Completion of error handling
Date: Tue, 16 Feb 2010 11:56:48 +0100	[thread overview]
Message-ID: <4B7A79F0.1070100@op5.se> (raw)
In-Reply-To: <4B740153.4010600@web.de>

On 02/11/2010 02:08 PM, Markus Elfring wrote:
> 
>>
>> 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
> 

That's an awful lot of text to read that's hardly relevant for a C
program. Most of it regards newbie stuff about how to handle reporting
an error when you can't use a C++ exception.

> 
> 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.
> 

You keep on claiming that but haven't proven it in any way. If you
could point out a real bug I'm very, very certain it would be fixed
within 24 hours.

> 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/
> 

Git is written in C, not C++. Using aspectc++ would mean requiring
the use of a C++ compiler, which git doesn't require today. That's
one step backwards in portability which I seriously doubt the
usefulness of aspectc++ can outweigh.

Now please stop trolling and find one of these bugs you keep talking
about but never showing. We've made it painfully clear to you that
we're interested in realworld problems rather than potential ones,
so all this "use this model for development" just reeks of concept
evangelism. No real engineer likes that, which is why you're facing
such massive opposition on this list.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.

  reply	other threads:[~2010-02-16 10:56 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
2010-02-16 10:56     ` Andreas Ericsson [this message]
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=4B7A79F0.1070100@op5.se \
    --to=ae@op5.se \
    --cc=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).