libobjc2 1.0 - a couple of problems

Just playing around with this now on FreeBSD, and came across a couple of curiosities. Firstly, the code only compiles with clang, not with gcc. When I try it I get these errors... selector_table.c: In function 'add_selector_to_table': selector_table.c:244: warning: passing argument 2 of

Re: NSCalendar and NSLocale support

I would concur, but IIRC from when I looked at it a couple of years ago, there is basically a pure C API and a C++ API side-by-side. The Just to save you some time, don't use the C API, as it doesnt work properly. I went through this a couple of weeks ago. Did a C version, got odd results,

Re: Grand Central

http://images.apple.com/macosx/technology/docs/GrandCentral_TB_brief_20090608.pdf Interesting - that ^{ syntax to describe a block is somewhat ugly, and it doesnt give any deats of how you associate data with a block (which is necessary if you want to get rid of locks). It still all looks a bit

Re: Fwd: [cfe-dev] Blocks runtime

We have an implementation of a blocks runtime (minus support for GC) in =C9toil=E9's ObjectiveC2.framework, but now Apple has released theirs under a BSD-style license. Very interesting - whait's this 'libgcc replacement' they are talking about ? wil that include the Obj-C runtime too ? It

Re: GNUstep base almost builds with clang

./runtest.sh base/NSProxy/test01.m not so good sadly... This is gnustep-make 2.0.8. Type 'gmake print-gnustep-make-help' for help. PASS: Proxy signed char PASS: Proxy unsigned char PASS: Proxy signed short PASS: Proxy unsigned short PASS: Proxy singed int PASS: Proxy unsigned int PASS: Proxy

Re: GNUstep base almost builds with clang

Both, they are moving over to clang (and LLVM) witness the subject line :). good stuff ;-) I should go re-visit llvm and clang really, I never took a proper look at it - I didn't realise it couod compile to native code, which is preseumably true if they are compiking a full OS with it [ thats

Re: GNUstep base almost builds with clang

Would it be possible for you to check whether GNUstep works with libffi? On FreeBSD/i386, it defaults to using ffcall, but works better with libffi (i.e. doesn't randomly corrupt the stack when you pass NSInvocations between threads). You probably need to explicitly specify

Re: GNUstep base almost builds with clang

Clang is a new front-end for LLVM, written completely from scratch, which is more-or-less feature complete for C99 and Objective-C 2 (parsing anyway - code generation is only finished for the Apple runtimes), and now working towards C++ support. Is this what you were using to try and

Re: GNUstep base almost builds with clang

Not sure what you are using to compile here. There is not FreeBSD port for clang, and trunk clang requires trunk LLVM (i.e. not the port). Can you tell me what commands you are trying to use to compile? I installed llvm-dev from ports. Which gives me a 'clang' command that I can use like

Re: GNUstep base almost builds with clang

Patch to fix this problem is here if you want to apply it to your local tree: Just working out how to get a local tree ;-) Aside from GNUstep I usually just build from ports. As far as I know, you are the first person to test clang Objective-C support on a 64-bit platform. Please keep

Re: GNUstep base almost builds with clang

From the mailing list when I asked this last, and from comparing the list of supported platforms for the two. Again, can you name one platform supported by ffcall and GNUstep, but not libffi? Does anyone want to jump in and say 'My platform doesn't support libffi! Please don't

Re: GNUstep base almost builds with clang

Well if your business depends on it, you might want to hire someone someone to do the development. Well, that would be me. But I kind of have a lot of other stuff to do. I'll reprhrase it as I dont want to take this on myself. Apple has moved away from GCC so you can no longer depend on them.

Re: GNUstep base almost builds with clang

Would it be possible for you to check whether GNUstep works with libffi? On FreeBSD/i386, it defaults to using ffcall, but works better with libffi (i.e. doesn't randomly corrupt the stack when you pass NSInvocations between threads). You probably need to explicitly specify

Re: GNUstep base almost builds with clang

I should have said moving away but really they are so close to have moved away, it can be considered moved. So what have they moved to out of interest, or can't you tell us ? Is this just for Obj-C or the whole operating system ? -pete. ___

Re: SIGSEGV at Unicode.m:1564

can you send me that again - it's in a bit of code I wrote, but the email inadventedly got deleteed when I wwas just looking at it! Any idea what the string is there ? -pete. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org

Re: amd64 and libffi

I got a report from a Debian user that GNUstep programs segfault on the amd64 architecture when gnustep-base is compiled with libffi. (On the other hand, GNUstep programs apparently don't work with ffcall on Opterons, since ffcall doesn't seem to play well with the NX bit, apparently.)

Re: GNustep make and fat binaries

Why not compile the binaries separately and combine them with lipo? thats what we ended up doing, but it woudl be nice to be able to produce fat binaries directly just like you can on OpenStep. am trying to find the time to take a look at this. ___

Re: Problems with a custom constant string class

Is there any way I can have a constant string class that can subclass anything other than `Object'? Yes, as long as the thing you are subclassing from doesnt have any instance variables, as it has to have a specific layout on the stack. That can make doing some things a bit fiddly, but it does