(
Jump to the original submission)
Sun 11 Mar 2012 11:38:57 AM UTC, comment #10:
I would prefer the acceptance clarification before the transformation of an agreement into source code.
|
Sun 11 Mar 2012 11:31:10 AM UTC, comment #9:
Clone the code, make the changes would like to see, and then let's discuss.
|
Sun 11 Mar 2012 11:05:14 AM UTC, comment #8:
I guess that the general acceptance needs to be clarified a bit more here for the adoption of improved techniques.
- Your CDIO library uses only the C programming language so far. It would be nice if C++ exceptions can be applied in function implementations eventually.
- The affected source files can be fixed manually. But I would prefer to encapsulate error handling as an aspect which will be automatically weaved into the target source code by the evolving tools.
|
Sun 11 Mar 2012 10:44:48 AM UTC, comment #7:
I am glad to hear that some of your suggestions somewhere have been used. But you really didn't answer my question.
I too have made numerous suggestions to projects which were used. It's nice when that happens. However more often you will find that if you want your ideas adopted, you'll have to involve yourself more and put forth the effort the see things through.
|
Sun 11 Mar 2012 10:30:37 AM UTC, comment #6:
I checked the acceptance for the mentioned techniques with a couple of other free software developers.
A few of my suggestions had an effect like it happened for the tool "AspectC++".
|
Sat 10 Mar 2012 11:13:16 PM UTC, comment #5:
Impossible to say in the abstract. Is there an open-source project you have worked on to show as an example?
|
Sat 10 Mar 2012 09:45:01 PM UTC, comment #4:
How are the chances to integrate any of the suggested means into the build infrastructure for your software?
|
Sat 10 Mar 2012 08:30:29 PM UTC, comment #3:
The direction libcdio takes is strongly influenced by the interest in and involvement of the individuals such as your self.
libcdio is an open-source project maintained in a distributed version control system. As such, I encourage you to "clone" the project and those changes that you find beneficial. Most likely, if these changes are deemed good by the community, they will be enthusiastically adopted. And where there is a question or concern, that would probably be discussed openly, probably on the libcdio development mailing list.
|
Sat 10 Mar 2012 07:00:46 PM UTC, comment #2:
Would you like to reduce the efforts for error code checking by an exception class hierarchy?
How do you think about to apply aspect-oriented software development for this use case?
|
Wed 07 Mar 2012 06:29:46 PM UTC, comment #1:
Submit a patch for this. Thanks.
|
Wed 07 Mar 2012 05:33:27 PM UTC, original submission:
I have looked at a few source files for your current software. I have noticed that some checks for return codes are missing.
Would you like to add more error handling for return values from functions like the following?
|
(Note: upload size limit is set to 16384 kB, after insertion of the required
escape characters.)
Attach File(s):
Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Follow 4 latest changes.