Menu
▾
▴
basilisk-devel
|
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.' | |
|
From: <ni...@in...> - 2001-07-02 01:34:48
|
Gwenole wrote: > 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. I commented: > 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) Gwenole said: > No, they will have "C" linkage because they would have been declared as > such (extern "C"). If you insert #ifndef __cpluscplus__ wrappers, wouldn't the declaration depend on the compiler which is processing them, and thus vary between the .cpp and .m files? Apple copyright stuff deleted ... > > 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 > > OK if that's a problem, I will keep the "unix" version if it works. I > haven't tried it yet with my Darwin/X11 port. The unix version works, but because OS X uses different conventions for storing the resource and finder files, it isn't very useful. i.e. You cannot access programs stored on MacOS X mounted HFS volumes. The structures I put in extfs_MacOSX.cpp are similar, copyright wise, to the stuff in macos_util.h. They are based on information published by Apple (whether from Inside Macintosh, or from the Apple Universal Headers). I suspect that if we rename or obfuscate the stuff I have typed in, that will be enough to get around any copyright issues. But then again, I am not a lawyer, and Apple might be monitoring this very mailing list :-) I wrote: > What if I produce a parody of the happy face, like a wrinkled > old version thereof? Christian answered: > > B2 is not a wrinkled version of anything! ;-) True, but B2 emulates an old Mac, running an old MacOS. That is what it could mean. Or maybe something like a bank vault or a museum? Something that stores old stuff? (both shiny-new, of course!) -- | 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.' | |
|
From: Christian B. <cb...@st...> - 2001-08-13 14:29:15
|
Hi! On Mon, Jul 02, 2001 at 11:33:23AM +1000, ni...@in... wrote: > [B2 logo] > Or maybe something like a bank vault or a museum? > Something that stores old stuff? (both shiny-new, of course!) I probably should contact the guy who already designed a B2 logo... Bye, Christian -- / Coding on PowerPC and proud of it \/ http://www.uni-mainz.de/~bauec002/ |
|
From: <gb...@di...> - 2001-06-29 10:39:23
|
Hi, > 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? I don't know, I will try to dig more info on the GNU site. > > 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. >=20 > 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) No, they will have "C" linkage because they would have been declared as such (extern "C"). > 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.) There are classes for serial emulation for example (in os-specific parts however) and some bits of STL now. In my experiments with Reversed Address Space, I do use operator overloading as well (that's not in CVS though). > 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 OK if that's a problem, I will keep the "unix" version if it works. I haven't tried it yet with my Darwin/X11 port. > What if I produce a parody of the happy face, like a wrinkled > old version thereof? I don't know. Christian said some time ago that someone was to contribute a nice icon but nothing appeared since. I think there are artists as B2 users, they would probably be pleased to contribute one if we ask them ? ;-) Bye, Gwenol=E9. |
|
From: Christian B. <cb...@st...> - 2001-06-29 13:55:46
|
Hi! On Fri, Jun 29, 2001 at 07:10:49PM +1000, ni...@in... wrote: > 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. As the author of a program, you are of course free to issue different licences to different people. > 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.) As a general warning, however, I intend to use more C++ in the future, where appropriate (one thing I'm planning is to rewrite the prefs module to use a map<>). > What if I produce a parody of the happy face, like a wrinkled > old version thereof? B2 is not a wrinkled version of anything! ;-) Bye, Christian -- / Coding on PowerPC and proud of it \/ http://www.uni-mainz.de/~bauec002/ |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X