From: SF Markus Elfring <elfring at users.sourceforge.net>
To: powertop@lists.01.org
Subject: Re: [Powertop] Completion of error handling
Date: Sat, 01 Nov 2014 13:00:26 +0100 [thread overview]
Message-ID: <5454CB5A.5070309@users.sourceforge.net> (raw)
In-Reply-To: 20141101105251.GA31366@sara.bahnhof.se
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
>> Would it be acceptable to integrate a tool like "AspectC++" into the build
>> process for your software?
>> http://aspectc.org/
>
> I think it would be a severe mistake - even if AspectC++ is an excellent tool
> it is a tool that almost nobody (well, save for you) knows about and so I
> would say it adds a big cost to contributing to the project.
Thanks for your feedback.
How are the chances to delegate more software maintenance tasks to dedicated
development tools?
> So, why would you want it?
Would you like to build programs that are more flexible and secure together?
Do you want to achieve benefits from the aspect design dimension?
> Convince us!
I try that again. I hope that you like to consider a few improved approaches.
How do you think about to improve static source code analysis also for your
software?
https://en.wikipedia.org/wiki/List_of_tools_for_static_code_analysis#C.2FC.2B.2B
Do you find information sources like the following useful?
* Article "A Reusable Aspect for Memory Allocation Checking"
http://aspectc.net/ac_tutorial.html#reusablemachecking
* Document "Aspect-Oriented Software Development - An Introduction"
by Johan Brichau and Theo D'Hondt
http://www.info.ucl.ac.be/~jbrichau/courses/introductionToAOSD.pdf
* Paper "On Typesafe Aspect Implementations in C++"
by Daniel Lohmann and Olaf Spinczyk
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.125.2164
Regards,
Markus
next reply other threads:[~2014-11-01 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-01 12:00 SF Markus Elfring [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-01 10:52 [Powertop] Completion of error handling Magnus Fromreide
2014-11-01 9:06 SF Markus Elfring
2014-10-31 23:19 Alexandra Yates
2014-10-31 7:08 SF Markus Elfring
2014-10-18 20:10 SF 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=5454CB5A.5070309@users.sourceforge.net \
--to=powertop@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.