Re: GDL2 on MacOS X

Just for the lis records...

On Mon, 18 Nov 2002 18:44:55 +0100 Stéphane Corthésy <[email protected]> wrote:
 >| I have some questions now:
 >| - What is the current state of gdl2?? How compatible is it with EOF 2? 
 >| WebObjects 4.5's EOF implementation?

        WO 4.5.x


 >| - Do gdl2 developers plan to support MacOS X? If they reply "no", no 
 >| need to read remaining questions ;-)

        I'd like to see it ported to MacOS X. I can provide some help to explain things,... 
But today, I can't make the port by myself. May be other gdl2 people or MacOS X people.

 >| - Does it even compile on a GNUStep system?? I had to correct some 
 >| code, independant of platform.

Yes, it compile well on my computer. But with a previous version installed 
(I haven't tried from scratch).
It run pretty well too :-) I use it with 60 entities.

 >| - gdl2 depends on GNUStep-specific classes, like GCArray, etc. Can this 
 >| dependency be removed? There are also references to methods not 
 >| implemented in MacOS X, like subclassResponsibility:, but in these 
 >| cases we could implement categories on MacOS X for GNUStep 
 >| compatibility.

gdl need GarbageCollection for some parts. I don't know if/how it works on Mac OS X


 >| - gdl2 is not consistent regarding retain/release and garbage 
 >| collecting; sometimes macros are used for retain/release, sometimes 
 >| method calls are used. How should it be done?

Concerning GC, I don't think so: there's part where GC is needed 
(see above) and parts where retain/release or GC could be used. 
I don't see how GDL2 could avoid garbage colection or similar mechanism.
 See http://www.gnustep.org/resources/documentation/gdl_2.html 
     (Resolving cycles within your model. A garbage collector)
Concerning macro, you are probably right, we'll improve this.


 >| - EOControl and EOAccess were 2 different frameworks in EOF, and 
 >| EOControl had no dependency on EOAccess. In gdl2, this is no longer the 
 >| case...

It's just the 1st release :-)

 >| - On MacOS X, there is now a NSClassDescription class, and categories 
 >| on NSObject implementing -entityName, etc. This means that either 
 >| GNUStep should implement them all (if not yet done?), or we should 
 >| rewrite that part for MacOS X. Conflicting categories are no good.

This should be probably implemented in GNUstep. We need to discuss with GNUstep base main developpers.


Manuel