[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: "multiple inheritence" / behavior

From: Richard Frith-Macdonald
Subject: Re: "multiple inheritence" / behavior
Date: Mon, 18 Nov 2002 11:25:25 +0000

On Monday, November 18, 2002, at 10:54  am, David Ayers wrote:

Alexander Malmberg wrote:

IMO, behaviors is (yet another :) useful and neat feature objective-c
gives us. It is perhaps a bit too advanced for us to plug extensively,
but the header should be installed (or moved to libobjc and installed by
it instead?), although I think the warnings should remain there.

I'd like to second this motion...

I noticed that we seem to have two versions of behavior.m active at the moment.
and the seem rather different.

The extensions library is (unless things have changed) not an official part of GNUstep ... the code has never been contributed to the FSF as far as I know, and has neve been supported as part of GNUstep. I've spent a chunk of the weekend going through the gdl2 code to remove any dependencies on the extensions library and might get round to providing a patch to do that soon (I'm a bit hampered by being unfamiliar with gdl2 and having no test code to see if it still works after my changes).

This discussion leads me to believe that we soon might have yet another behavior.m in another library of framework. (Manuel?)

I understand that this is a very advanced feature and I personally have decided to avoid it as much as I can, due to some of it's debuging implications, but it does seem to make sense in certain situations. Therefor I wish to second Alex's proposal to make behavior.h public (in base for now, depending on whether it should ever be part of objc) and use one version consistantly.

I think the behavior.h file has always been public in the base library. It is installed in /usr/GNUstep/System/Headers/gnustep/base along with most other non-Foundation headers, but It's not documented though, and the comments in the source/headers warn about using it ... probably that should be changed (ie. documentation added and warnings updated/clarified).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]