I am sorry, but your suggestions are not very useful for our project at this point.
If you want to contribute, please send something concrete (a patch for a bug or an implementation of a feature in the projects file) rather than sending me homework to do. Regards, Kern On Sunday 29 November 2009 10:02:00 SF Markus Elfring wrote: > > I am not interested in using AspectC++. It is just one more concern for > > porting and at this point in time will consume time for "cleanup" when we > > need all the time we can get for "implementation" > > I suggest to raise the abstraction level. > http://en.wikipedia.org/wiki/Abstraction_%28computer_science%29#Abstraction >_in_object_oriented_programming > > > It depends also on the willingness to apply appropriate software tools. > Tools like AspectC++ exist to save programming work because some source > code can be automatically generated for you on demand. > > > The few new operators we use will probably be removed, and there is > > absolutely no chance that we would even consider the STL. > > It is a pity that you want to move away from C++. > http://www.bacula.org/3.0.x-manuals/en/developers/developers/Developing_Bac >ula.html#SECTION00268000000000000000 > > > > Would you like to reduce the efforts for error code checking by an > > > exception class hierarchy? > > > http://dietmar-kuehl.de/mirror/c++-faq/exceptions.html#faq-17.1 > > > > No. Our current error code handling works across all platforms and does > > not require us to check return codes everywhere. > > The C programming language makes it inherently easy to overlook specific > implementation details. Wrapper functions can improve the error detection. > I have got the impression that the current approach is incomplete. > > > We are not interested in adding many more object and aspect oriented > > features. > > You reject some techniques in this way to reduce work ... > > > If you can find outright bugs, you would be doing the project a big help. > > I would like to point out the risk for omission of some exception handling. > > > For the moment, we cannot even think about trying to take on more C++ > > features. > > I would prefer a different mixture of C and C++. C will still be required > to provide the application binary interface for the part of your software > which belongs to your reusable library. > > Regards, > Markus ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
