I'm having problems using "new-style" exceptions with GNUstep on
FreeBSD 6.2 (amd64). I have the following program (main.m):
#include
int main(int argc, char ** argv) {
@try {
@throw nil;
} @catch (id thing) {
printf("caught!\n");
}
}
which run
<[EMAIL PROTECTED]> wrote:
make messages=yes
will display exactly the command-line commands used to compile and link; you
may
want to try it out and compare those with the ones you use yourself ... that
might
provide some light on what the problem could be. :-)
Thanks
-Original Messa
On 3/15/07, Andrew Pinski <[EMAIL PROTECTED]> wrote:
You still have to compile your program with -fexceptions to get "objc"
exceptions working with objective-C.
But that doesn't explain (2), where I *do* use -fobjc-exceptions, only
with gcc instead of g++, and with a separate linking step inste
On 3/15/07, Richard Frith-Macdonald <[EMAIL PROTECTED]> wrote:
Presumably you failed to use the --enable-native-objc-exceptions when
configuring gnustep-make.
It's hardly surprising that the wrong flags are being passed to the
compiler and the wrong config options being set if the system was not
D'oh! I forgot to attach config.log, after I accidentally reloaded the
window in which I was writing the previous email and had to re-type
the whole thing. Sorry about the noise.
-Michael
On 3/15/07, Michael Gardner <[EMAIL PROTECTED]> wrote:
On 3/15/07, Richard Frith-Macdon
On 3/15/07, Nicola Pero <[EMAIL PROTECTED]> wrote:
I believe that Andrew is suggesting trying
-fobjc-exceptions -fexceptions
both when compiling and linking. Can you try it out ?
Ah, I misread; sorry about that. I just tried that suggestion:
gcc41 -c -fobjc-exceptions -fexceptions
-I$GNUST
On 3/15/07, Andrew Pinski <[EMAIL PROTECTED]> wrote:
On 3/15/07, Richard Frith-Macdonald <[EMAIL PROTECTED]> wrote:
> I thought that compiling with '-x objective-c' was supposed to have
> the same effect as compiling a file with a .m extension too.
> If that understanding is correct, I don't see
On 3/15/07, Andrew Pinski <[EMAIL PROTECTED]> wrote:
On 3/15/07, Michael Gardner <[EMAIL PROTECTED]> wrote:
> That bug's description doesn't seem to match the symptoms I'm seeing,
> and it's reported against gcc 4.3 rather than 4.1.
For one, it is the sa
Thanks to everybody for your help.
On 3/17/07, Nicola Pero <[EMAIL PROTECTED]> wrote:
That's brilliant ... I added --shared-libgcc (on all platforms) to the
linking stage when
native ObjC exceptions are enabled. :-)
Hopefully that fixes it ... Michael, any chances you could try it out with
gnus
Thanks for the tips. I just installed GNUstep from trunk, and can
confirm that the problem is fixed. :)
-Michael
On 3/19/07, Nicola Pero <[EMAIL PROTECTED]> wrote:
>> That's brilliant ... I added --shared-libgcc (on all platforms) to the
>> linking stage when native ObjC exceptions are enabled
To use a custom key type with NSMutableDictionary, I defined -hash and
-isEqual: but not -copyWithZone:, since the NSDictionary docs say that
keys are retained rather than copied. But when I try to insert a key
of that type, I get an NSInvalidArgumentException saying that my class
does not recogni
I've got some code in an NSImageView subclass that looks like this:
-(void) mouseDown: (NSEvent*)event
{
...
[self dragImage: [self image] at: NSZeroPoint offset:
NSZeroSize event: event pasteboard: pboard source: self slideBack:
YES];
...
}
and in the dragging destination,
happens in trunk; the latest release is
fine. But the trunk builds have been doing this for a while now, and
I'd like to make sure that if this is a bug, it doesn't get into a
release.
-Michael
On 4/26/07, Fred Kiefer <[EMAIL PROTECTED]> wrote:
Michael Gardner wrote:
> I'
se it will be hard to
explain the result you are seeing. I need to set this myself to see if I
am able to reproduce the problem.
I haven't modified that setting, so presumably it's still at its
default value. How can I verify this?
Fred
Michael Gardner wrote:
> Thanks for the response
On 4/30/07, Richard Frith-Macdonald <[EMAIL PROTECTED]> wrote:
The coordinates returned by the -draggedImageLocation method are the
coordinates of the bottom left corner of the image in the base
coordinate system of the window receiving the drag. That means you
need to do 'dropPoint = [dropView
I'm allocating objects with class_createInstance(), storing them on a stack (well, just a plain NSArray), and popping them off at a later time. When I pop an object from the stack, it gets released (as I expect), but I get a segfault from -[NSObject dealloc] that I can't track down.
I'm pretty sure
forgot that class methods in Obj-C realy are just instance methods of a Class object. Got some unlearning to do, it seems...
Thanks!MikeOn 5/18/06, Markus Hitter <[EMAIL PROTECTED]> wrote:
Am 18.05.2006 um 07:18 schrieb Richard Frith-Macdonald:>> On 18 May 2006, at 05:31, Michae
17 matches
Mail list logo
