Marco Bleich wrote: > These are still on the todo list: >> a) 'concordance.c:21': should be: #include "../libconcord/libconcord.h"?!
No, it should be #include <libconcord.h> Fixed in my local copy, will get commited when I finish up the firmware stuff I mentioned in the last email >> b) 'concordance.c:25': move to #include <libgen.h> to the non-WIN32 Really? Damn, ok, done in my local copy, will be committed. >> section. >> c) 'libconcord.def/libharmony.def': rename 'lh_strerror' to 'lc_strerror' >> d) 'libconcord.def/libharmony.def': add 'delete_blob' >> e) 'libconcord.def/libharmony.def': add 'is_config_safe_after_fw' Done in my local copy. > And of course the "<bad word deleted>-Microsoft-ANSI-C" issue! <:-)) Yeah, that's on the list (I just made a TODO in the concordance directory and put that in there). Bleck. -- Phil Dibowitz [EMAIL PROTECTED] Open Source software and tech docs Insanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
