* De: Chad David <[EMAIL PROTECTED]> [ Data: 2002-10-30 ]
[ Subjecte: Re: Objective-C threads ]
> On Wed, Oct 30, 2002 at 09:22:21AM -0800, Juli Mallett wrote:
> > * De: David O'Brien <[EMAIL PROTECTED]> [ Data: 2002-10-30 ]
> > [ Subjecte: Re: Objective-C threads ]
> > > On Wed, Oct 30, 2002 at 09:23:53AM -0700, Chad David wrote:
> > > >
> > > > Which brings us back to my original question... why are ObjC threads
> > > > disabled? I don't much care about my other patches, I just want
> > > > to know who the 10 others are who will break if we enable threads,
> > > > and how to fix that breakage. My minor patches were only posted because
> > > > you asked :).
> > >
> > > I am not sure. But for some reason you didn't provide a patch that would
> > > turn them on. All you provided was a minor patches that really should go
> > > thru the offical FSF GCC repo in-route to FreeBSD. So back to my
> > > original request. Do you have a patch for changing this part of the way
> > > we configure and build ObjC that you feel might be wrong?
> >
> > With a simple test program,
> >
>
> [cut]
>
> >
> > obj = [Test alloc];
> > [obj set:"Threads"];
> > pthread_create(&td, NULL, thr, NULL);
>
> This will work the way FreeBSD currently builds ObjC, what I want
> to use is objc_thread_xxx() and friends, so that the code maintains
> portability, and the runtime is kept up to date with what is going
> on.
My point was it doesn't break currently working things in a threading
case. Your observations of the real issues are, of course, correct :)
When you're chattign with the gcc objc people, get them to fix the nit
in README.threads or THREADS where it says if you have a thread-aware
GCC you can use thr-gcc.c... That file does not seem to exist, at
least not in our contrib sources.
juli.
--
Juli Mallett <[EMAIL PROTECTED]> | FreeBSD: The Power To Serve
Will break world for fulltime employment. | finger [EMAIL PROTECTED]
http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking!
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
