[systemd-devel] Completion of error handling

[SF Markus Elfring]

> I have no understanding of Coccinelle.

This software provides the tool "spatch" which lets you specify transformations
for C source code in a similar way you are used to already by the reuse
of unified context diffs.
http://coccinelle.lip6.fr/

I assume that you have eventually noticed specific updates on Linux source files
which were automatically generated by this technology.
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tree/Documentation/coccinelle.txt?id=refs/tags/v4.1.3


> I do not understand what you are saying.

How do you think about to try the shown small source code analysis script out
so that you can see from a generated patch directly where another look
might be useful?


> Generally, please be specific, provide patches.

I suggest to consider additional "patch formats" as a better preparation
for software improvements.

The Coccinelle software concentrates on the support for collateral evolutions.
A specific update suggestion can be written as "a diff script".
Each diff targets only a concrete kind of software evolution.

But there are methodologies evolving which support the encapsulation
of cross-cutting concerns directly.
Such known concerns are for example:
* Logging
* Error detection and corresponding exception handling

Would further considerations be acceptable around a tool like "AspectC++"?
http://aspectc.org/


> We are much more interested in actual technical contribution,
> much less in just talking about stuff.

I propose to integrate higher level algorithms and procedures into
the software build process so that some manual software maintenance tasks
can be reduced.
Would you like to give thoughts for the extension of the software development
toolbox a chance?

Regards,
Markus