Re: GNUstep tarball archive

2009-07-13 Thread Atanas Bombov
On Friday 10 July 2009 16:36:21 you wrote:
 On Jul 10, 2009, at 7:19 AM, Atanas Bombov wrote:
  Hi everyone,
 
  I am looking for older (pre- 0.12 and 1.12) versions of the core
  libraries, is there a place where
  the old versions are being kept? I couldn't find them on the main
  site...

 I don't know if anyone has kept those, but you can always go back in
 SVN and checkout previous versions.  Browse SVN to see which tags were
 used (generally lib-major_minor_subminor, e.g. base-1_12_0):

 http://svn.gna.org/viewcvs/gnustep/libs/base/tags/

Hello Adam,

Thanks for the advice. Still, I think it's good to have an archive with all 
GNUstep releases, IMHO. 
I found one such external archive here: 
http://debian.uni-duisburg-essen.de/misc/GNUstep/CoreAll/ 
. It could be used to create an official one - if you decide so.

Thanks,

Atanas


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev


Re: New gui/back release?

2009-07-13 Thread Adam Fedor


On Jul 11, 2009, at 6:38 AM, Fred Kiefer wrote:


As we are about to the the big change to NSSound from Stefan Bidigaray
and new code tends to need a few weeks to get most of the bugs out,  
I'd

like to propose that we release a new version of gui and back before
that. There already a quite a few bug fixes in both that would  
justify a
release already. And I hope to find the time to look at a few more  
bugs

the next days.



The last release was about two months ago, and that's a pretty good  
time frame to make a new release.



___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev


Memory Management

2009-07-13 Thread Stefan Bidigaray
I'm debugging the NSSound stuff and have run into a bit of a problem with
memory management and the whole RETAIN/RELEASE stuff... I'm sure my probably
has do to with being a novice.

Anyway, in the -dealloc method of NSSound I call RELEASE(_data) and right
after it [nameDict removeObjectForKey: _name].  The dictionary nameDict
contains as a key the sound name and as a value the NSSound object
associated with it.  Well, whenever this method is called it will go ahead
and call NSSound's -dealloc again which in turn sends another call out to
RELEASE(_data).  As you can imagine it blows up at this point.

So my question is:  Would adding a RETAIN(self) just before the call to
[nameDict removeObjectForKey: _name] solve this issue?  Anything else?  This
seems to do the trick, but I'm wondering if it's correct.

Thanks
Stefan
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev