Stefan Urbanek wrote:
Hi,
There were many talks about 1.0 release of GNUstep. Many of participants
argued, that the GNUstep is not ready for the 1.0 release. Can someone
who know the internals say, what exactly is needed for the release?
Sorry to sound very stupid, but I have a few basic problems.
Frederico Muñoz wrote:
Warning, long and boring mail ahead.
I have a doubt about the best way to display a progress bar when the
actions that will affect the progress movement are inside a loop.
[...]
I decided to use:
[NSThread detachNewThreadSelector:@selector (installPackage:)
toTar
Speak up, people.
We have a GNUstep app that run on both windows/mingw and unix.
Path handling have been a pain all the way. We had to patch the GNUstep
library to get a correct behavior (this was a few years ago. With
current versions of GNUstep, we don't have to patch anymore). We did not
send
Frederico Muñoz wrote:
The problem I'm having is that when I deserialize the data into a NSDictionary to perform the copy operations that
> filenames appear in random order,
NSDictionary's keys are not oredered. You should order them yourself.
If alphabetical order is fine, then, instead of:
NSEnum
Frederico Muñoz wrote:
Thanks, I stumbled upon this methods while searching for a solution, and your mail made me understand the usage better.
Pleased to have helped.
> It doesn't apply to my situation, since the order is not alphabetic,
> but it was good info nonetheless.
Well, in alphabetical or
Hi all,
I am sending this to gnustep-dev crossposted to gcc. Maybe this isn't
the right mailing list. See at the end of the post for a 40 line program
that exhibit the bad behavior.
Problem:
If a is a fault (ie: changes its isa pointer during forwardInvocation),
then:
[a method1:[a method2
Jeremy Bettis wrote:
- Original Message - From: "Frederic Stark" <[EMAIL PROTECTED]>
To: ;
Sent: Tuesday, June 21, 2005 6:12 AM
Subject: Problem implementing faults in Objective-C
: Uncaught exception NSInvalidArgumentException, reason: B(instance)
does not recognize
Timothy J. Wood wrote:
[crunch]
The code works correctly under Mac OS X.
I just checked under linux/gcc 3.4 and the code works fine there. Maybe
this is a gcc 3.2 specific problem. I'll check gcc 3.4 windows one of
those days.
The Apple runtime doesn't have this design choice, so it can'
