[Mono-osx] [ANN] mcocoa 0.7 and mobjc 0.8

Jesse Jones jesjones at mindspring.com
Sun Jan 10 18:23:17 EST 2010

On Jan 8, 2010, at 2:16 PM, Lee V. Andrus wrote:

> Looking into your makefile, I found that the dependencies of some targets
> (including "all") are backwards.  Although dependencies and/or rules between
> such dependent targets usually force them to be built in the correct
> sequence, it may be prudent to list multiple dependencies of a target in the
> sequence you would prefer or expect them to be built.

Thanks for the tip. I'll review them.
> On another note, I noticed that there are still no wrappers classes or
> interfaces for Objective C Protocols, although their methods are wrapped in
> each class that "conforms to" them.  Methods in Category
> NSDraggingDestination each have a parameter of type "id <NSDraggingInfo>". 
> Since no class that conforms to that Protocol is exposed in the framework
> header files, nothing about it is generated by your generator.  I will
> probably need to create my own set of extension methods to handle this.

This has been on my list of things to do, but it's been a rather low priority because I have never come across a use case where I thought it would be useful. If you don't mind my asking, where do you think they would be useful?
> As for the future development of MObjC/MCocoa, my vote would be for
> enhancing the automatic generation to handle variadic methods,

I think that this would require rewriting mobjc's slow path (which is not a bad idea in any case).

> methods with
> function pointer or block parameters,

I'll look into doing this for the next version. The only reason I didn't before is that I didn't want to parse function pointer declarations. But I'm now using a generated packrat parser to parse headers so that problem has become a lot more tractable. I've also learned that Apple's frameworks include a file containing metadata for that framework which may prove useful.

> and wrappers for Protocols;

Right now I'm not planning on doing this anytime soon.

> and some
> form of build switch to target a specific OS X version.  

Yeah, the current situation is kind of lame. I'll look at doing a better job with this in the next version.

Thanks for the feedback (and apologies for the delay in replying, I've been extremely busy at work trying to get our software out of alpha).

  -- Jesse

More information about the Mono-osx mailing list