> > 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: - libharmony.def (libconcord.def): ; GENERAL REMOTE INTERACTIONS ; init_libconcord deinit_libconcord - libconcord.h: - /* * Initialize USB (and WinSock if necessary) and find the remote * if possible. */ int init_concord(); /* * Release the USB device, and tear down anything else necessary. */ int deinit_concord(); /* -
> > c) What is 'lh_strerror' and where is it defined? > > It's lc_strerror() now (got renamed in the... rename). It's defined the > same > place the rest of the API is defined. Ok. I Thought so. There are some references in concordance.cpp to 'lh_strerror'. Ill check that again. Still some more work to do. Btw. I think 'libconcord/win/getopt' should move to 'concordance/win/getopt' ------------------------------------------------------------------------- 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
