[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mono-osx
Subject:    Re: [Mono-osx] Monobjc and mobjc, confusion, duplicate work?
From:       Andrew Brehm <ajbrehm () gmail ! com>
Date:       2008-12-15 10:38:12
Message-ID: 21011543.post () talk ! nabble ! com
[Download RAW message or body]


Wow.

Have to try NObjective soon!

This is getting better and better.

Andrew (Happy User)


Eugeny Grishul wrote:
> 
> Recently I update license of NObjective to LGPL so commercial apps can now
> link with it. I can't change license to MIT X11 coz I want to be main
> developer of that library. I can specify separate license appropriate for
> using it on iPhone.
> 
> NObjective's class exporting system can be easily adopted to work without
> Reflection.Emit.
> But my code dynamically generates a lot of small chunks of x86/ppc machine
> code for each exported method that used for cross-runtime exception
> rethrowing ( like Mobjc project does via libffi. But my approach more
> efficient ) so it can be problem. Currently mono for iPhone not available
> so there is no way to test NObjective on it.
> 
> Also now my library internally have Objective-C lexer/parser (
> NObjectiveAST ) written in C# and with its support I can regenerate all
> objective-c proxies in few seconds.
> 
> WBR,
> Eugeny Grishul 
> 
> 
> Miguel de Icaza-2 wrote:
> > 
> > Hello,
> > 
> > > Hi. There is another one - NObjective (
> > > http://code.google.com/p/objcmapper/
> > > ) =)
> > 
> > It is worth pointing out that NObjective/Objcmapper is licensed under
> > the GNU GPL 3 license, which means that it can not be used for
> > commercial/proprietary software.
> > 
> > Both MonoObjc and Cocoa# are licensed under the terms of the GNU LGPL
> > which does allow you to link commercial applications with it, but will
> > be unsuitable for iPhone development due to the incompatibility of the
> > LGPL with the model that Apple has chosen for the iPhone.
> > 
> > I would love to see the code under the MIT X11 license for any of the
> > above as that is what we use for all of the Mono class libraries that we
> > develop at Novell though.
> > 
> > (The Apple iPhone will pose other problems, like it would not be
> > possible to use dynamic code like Cocoa# and MonoObjC do today as
> > Reflection.Emit is not available on Mono/iPhone).
> > 
> > Miguel.
> > 
> > _______________________________________________
> > Mono-osx mailing list
> > Mono-osx@lists.ximian.com
> > http://lists.ximian.com/mailman/listinfo/mono-osx
> > 
> > 
> 
> 

-- 
View this message in context: \
http://www.nabble.com/Monobjc-and-mobjc%2C-confusion%2C-duplicate-work--tp20599230p21011543.html
 Sent from the Mono - OSX mailing list archive at Nabble.com.

_______________________________________________
Mono-osx mailing list
Mono-osx@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-osx


[prev in list] [next in list] [prev in thread] [next in thread]