Stéphane Corthésy wrote:
Some more patches for GDL2.
Stéphane
Changelog
EOControl/EOControl.h: added inclusion of EODefines.h and
EOArrayDataSource.h
Thanks, I guess I lost the version that included EOArrayDataSource.h!
I'm reluctant to include EODefines.h. All headers that need it should
Stéphane Corthésy wrote:
Hi,
Three bugs in gdl2/EOAccess/EODatabaseContext.m:
- in setDelegate:, the == in the while loop must be replaced by a
single =
Thanks!
- in -relayPrimaryKey:object:entity:, the test if(isToMany) must be
done only if value != nil
This sounds sane, but I think I'll
David Ayers wrote:
As most code #including the header will want EONull to implement the
methods, but we are internally using NSNull, the switch is done only
in the implementation file. But maybe we should move the define
closer to the category implementation. Or be explicit about it in the
David Ayers wrote:
I know, but I was thinking that links are imlemented as copy. And since
the copy of the headers would be done after-all: it should not affect
the build porcess of the (sub)library but make the headers (and yes the
*.m files and all the rest also) available for the other
David Ayers wrote:
Hi,
ScriptKit
* Library/Guile.h: Use qualified gnustep/guile/header.h path for
inclusions. Use rather than for local inclusions.
* Library/GuileInterpreter.h: Use rather than for local
inclusions.
* Library/GuileScript.h: Ditto.
*
Stefan Urbanek wrote:
Another issue in gnustep FSH is that noone is using ApplicationSupport
directory. It is a good thing, because this will contain all possible
pollution of Library directory. And here I would like to ask, what
should i do with StepTalk? Currently it uses Library/StepTalk
Adam Fedor wrote:
David Ayers wrote:
Hi,
ScriptKit
* Library/Guile.h: Use qualified gnustep/guile/header.h path
for
inclusions. Use rather than for local inclusions.
* Library/GuileInterpreter.h: Use rather than for local
inclusions.
*
There seems to be a new memory leak in GNUstep that can be most easily
seen in GSTest.app.
1) Start up GSTest.app.
2) Select the Info Panel from the menu.
3) Start the Memory Panel by clicking the image.
4) Hit Update a few times.
You will notice that the number of GSUnicodeInlineString keeps on
Adam Fedor wrote:
Well, in the spirit of instability, API changes and incompatibilities
:-) I'm finally getting a good start on rearranging the filesystem as
described in:
http://www.gnustep.org/experience/documentation/filesystem.ps
Point by point:
ApplicationSupport: Just dumb. There
