From: <ni...@in...> - 2001-06-29 09:11:59
|
Gwenole asked: > > 1. License. Currently Nigel placed his code into Public Domain. I don't > think it is compatible with GPL. I will add the usual GPL header and add > Nigel's name in all sources he sent me. I need suggestions/agreements > here. I only labelled some of my code as public domain. Here are the ones that did not include a standard B2 GPL header: File Currently Comments ---------------------------------------------------------------- cpp_glue_MacOSX.h PD Fix it main_MacOSX.h & m PD Partially derived from Apple junk? video_MacOSX.h PD Fix it Controller.h & m None Fix it Emulator.h & m None Fix it EmulatorView.h & m None Fix it NNThread.h & m PD Not B2 specific, already released PrefsEditor.h & m None Fix it ================================================================ For most of the files, it doesn't matter. The only ones I would like to keep as PD are NNThread.h & m, as I have already e-mailed versions of these to developers on the macosx-dev mailing list. Is there some version of a license which _is_ compatible with GPL, but doesn't prevent prople from doing whatever they damn well please with the source files? (Probably not. I can't have it both ways. If necessary, I can e-mail those developers and tell them that from version 3 onwards those files are under GPL) > 2. Mixing C++ and Objective-C is not quite possible at the current time. > Therefore, Nigel implemented a few C wrappers. However, I think we don't > need them if we declare functions in src/include/*.h with "C" external > linkage. If this approach works, I will remove Nigel's C wrappers and > commit patched versions of includes with various #ifndef __cplusplus__ / > extern "C" clauses. 1) I think that will just cause link errors, as the files would have been compiled one way (as C++ interfaces, because they are in .cpp files), but referenced as another. (C interfaces in my Objective-C source) For this to work, all the B2 source would probably have to be moved into .c files 2) As a general observation, most of Balisisk II's source code _is_ actually C. (i.e. there are no classes, overloaded operators, et c.) If, in the future, the code is going to start passing objects around, then keeping it the way it is, and for OS X to use wrappers, is the only way to go. > 3. Naming conventions. File names currently have the form > extfs_MacOSX.<extension>. I'd prefer to lowercase them in order to be > consistent with the other ports. Doesn't matter to me. ... > 5. Icon. Though it looks really good, I don't think we can include it > because the background logo is the MacOS happy face. > <http://www.apple.com/legal/> I haven't looked at that site yet, but it could potentially be a problem, as could some of the structures I typed into extfs_MacOSX.cpp For the icon, maybe the makefile could generate it on the fly from the happy face in the installed OS? Would still be a problem for distributing a precompiled binary though. What if I produce a parody of the happy face, like a wrinkled old version thereof? > 6. Delays. I have a very busy week right now. So I am not sure if I > could patch/upload everything before next week. No hurry. -- | Nigel Pearson, ni...@in... | "Reality is that which, | | Telstra NW-D, Sydney, Australia. | when you stop believing | | Office: 9206 3468 Fax: 9212 6329 | in it, doesn't go away." | | Mobile: 0408 664435 Home: 9792 6998 | Philip K. Dick - 'Valis.' | |