• Jason House <jason.james.house gmail.com> Nov 03 2010
• Michel Fortin <michel.fortin michelf.com> Nov 04 2010
• Walter Bright <newshound2 digitalmars.com> Nov 06 2010

Jason House <jason.james.house gmail.com> writes:

Michel Fortin Wrote:

 I posted on my blog a preliminary document outlining what I intent to 
 implement in DMD to support the Objective-C object model.
 
 <http://michelf.com/weblog/2010/dobjc-preliminary-design/>
 
 Comments?


It looks like a few things are already implemented. I'd recommend submitting a
basic O-C patch and seek Walter's feedback. What's the minimal set of O-C
integration that would make your work usable? I'd try to get that in early and
incrementally improve functionality.

 
 
 -- 
 Michel Fortin
 michel.fortin michelf.com
 http://michelf.com/
 

Michel Fortin <michel.fortin michelf.com> writes:

On 2010-11-03 23:28:38 -0400, Jason House <jason.james.house gmail.com> said:

 What's the minimal set of O-C integration that would make your work 
 usable? I'd try to get that in early and incrementally improve 
 functionality.


That's a tricky question that depends on what you mean by "usable". I'd 
say that supporting extern (Objective-C) classes and interfaces and 
constructors is the minimal functionality to make things usable. But is 
it acceptable to put into mainline DMD something that is scheduled to 
work differently once I implement the rest, such as the memory 
management section with automatic reference counting?

I'm know I should release things early to let those interested test it 
and give me some feedback (and create bindings), but I'm not sure 
whether it should be merged into the trunk so early. With Walter's 
permission, I could publish my git repository to let people peek at the 
code. I haven't done so before because it's a clone of the SVN 
repository and it contains the backend too, which is under a less open 
license.

-- 
Michel Fortin
michel.fortin michelf.com
http://michelf.com/

Walter Bright <newshound2 digitalmars.com> writes:

Michel Fortin wrote:
 I'm know I should release things early to let those interested test it 
 and give me some feedback (and create bindings), but I'm not sure 
 whether it should be merged into the trunk so early. With Walter's 
 permission, I could publish my git repository to let people peek at the 
 code. I haven't done so before because it's a clone of the SVN 
 repository and it contains the backend too, which is under a less open 
 license.
 


You have my permission to do it as long as you don't change the license.

I think you are quite right to release this as an experimental fork until we're 
sure it's the right approach, rather than jack users around with fundamental 
changes.