Skip to contentSkip to conversation

Completion of error handling

Powertop SF Markus Elfring 3 participants 5 messages Oct 31, 2014 – Nov 1, 2014 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

SF Markus Elfring

author
#1 lore raw
Quoted 1 line

This is a good idea, please send your patches with the fixes.

I suggest to avoid ignorance of return values a bit more.
https://cwe.mitre.org/data/definitions/252

Are you interested to apply aspect-oriented software development? How do you think about to encapsulate error detection and corresponding exception handling as a reusable aspect in your software?
https://en.wikipedia.org/wiki/Aspect_%28computer_programming%29

Regards,
Markus

#2 lore raw
Quoted 6 lines
Quoted 2 lines

This is a good idea, please send your patches with the fixes.

I suggest to avoid ignorance of return values a bit more.
https://cwe.mitre.org/data/definitions/252

Quoted 9 lines

Are you interested to apply aspect-oriented software development? How do you think about to encapsulate error detection and corresponding exception handling as a reusable aspect in your software?
https://en.wikipedia.org/wiki/Aspect_%28computer_programming%29

Regards,
Markus

Hi Markus,

They are both great ideas to make PowerTOP more robust. Please sent your patches for review.

Thank you,
Alexandra.

author
#3 lore raw
Quoted 1 line

They are both great ideas to make PowerTOP more robust.

Would it be acceptable to integrate a tool like "AspectC++" into the build process for your software?
http://aspectc.org/

Regards,
Markus

#4 lore raw
Quoted 5 lines · SF Markus Elfring
Quoted 1 line

They are both great ideas to make PowerTOP more robust.

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.

So, why would you want it? Convince us!

/MF

author
#5 lore raw
Quoted 7 lines
Quoted 3 lines

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?

Quoted 1 line

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?

Quoted 1 line

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