Hello, I pointed out that return values from various function calls were ignored at some places in the source files. http://bugs.bacula.org/view.php?id=1405
I suggested a few design choices. Which ways are acceptable to fix the involved details? I would like to continue the discussion with the mentioned memory allocator. http://bacula.org/3.0.x-manuals/en/developers/developers/Smart_Memory_Allocation.html I see the requirement that all users of a malloc compatible API should generally deal with handling of null pointers. I find it strange that the C++ new operator is not used for this purpose in your class library. http://bacula.git.sourceforge.net/git/gitweb.cgi?p=bacula/bacula;a=blob;f=bacula/src/lib/bsock.c;h=a2e3bb275c47f9fa63ec0a7bb0f6df04b8f49459;hb=HEAD#l55 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
