[Openmcl-devel] Leopard interfaces / Obj-C 2.0 GC support
pbpublist at comcast.net
Fri Oct 26 17:26:01 PDT 2007
Thanks for the info. Do your comments re: the parser problem mean
that the current interfaces are broken/incomplete or that they work
but you aren't able to generate a new set for the GM release?
They just posted the GM version which I'm downloading now which
should at least make it possible to see what's changed since the last
beta as I've got a few minor breakage issues as well. At least I'll
soon know if the breakage was my code or the beta...
On Oct 26, 2007, at 8:16 PM, Gary Byers wrote:
> On Fri, 26 Oct 2007, Phil wrote:
>> So now that it's safe to talk about Leopard... can the Leopard
>> interfaces be released?
> The good news is yes; the ones that I've been using (which were
> in August) are now in
> The bad news is that the interface translator that I've been using
> together from Apple's Tiger gcc sources and some early ObjC-2.0
> that Apple committed to the GCC svn tree about a year ago) doesn't
> quite handle the current (last beta) Leopard Cocoa (AppKit/Foundation)
> headers and has had problems with other things (WebKit, etc.).
> Hopefully, the source to the version of GCC that Apple uses on Leopard
> will soon become available, and it'll be (relatively) simple to
> modify that source to produce .ffi output.
>> Also, I'm curious on what would be involved
>> and/or issues related to getting Clozure CL working with the Obj-C GC
> I don't know. I'm hoping that the source to the ObjC-2.0 GC (libauto
> ?) will also be made available and that it'll be easier to answer that
> question once that happens.
> (Disclaimer: I haven't looked to see if either the GCC sources or the
> libauto sources or any other Leopard component's sources are available
>> Openmcl-devel mailing list
>> Openmcl-devel at clozure.com
More information about the Openmcl-devel