Marco Bleich wrote: >>> a) I renamed 'libharmony.def' to 'libconcord.def'. Is that in line with >> the >>> "dibowitz-naming-conventions"? ;-) >> Crap, ANOTHER one I missed. I'll have to get SF to rename that one too. >> Bleck. Yeah, you're right, but it involves a ticket to SF. I'll do that >> now. >> >>> b) I replaced the symbols 'init_libconcord' and 'deinit_libconcord' with >>> 'init_concord' and 'deinit_concord' in the def file. Is that ok? >> No? Why? > Hmm... That's why:
Oh, good call. I fixed that in CVS, thanks. > Ok. I Thought so. There are some references in concordance.cpp to > 'lh_strerror'. concordance.cpp is deprecated and no longer used. See concordance.c. Once concordance.c has been built in windows and linux, I'll delete concordance.cpp. > Btw. I think 'libconcord/win/getopt' should move to 'concordance/win/getopt' Damnit. The SF guys are going to kill me. I added it to the ticket. -- 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
