Nicola Pero <nicola.pero <at> meta-innovation.com> writes: > > > >I don't have *any* experience in building dll > >And building gcc-libobjc as a dll might break some other thing... > >So i give up and let this task to others, even if i could not use > >'native exceptions'. > > Why do you need gcc-libobjc for 'native exceptions' ?
For esthetic reason ;-) And because i think compiler managed exceptions is an improvement over macro based exceptions. > Are there any missing changes in gnustep-objc ? > We could import a new fresh libobjc > into gnustep-objc to get any missing changes. Why does gnustep-libobjc prevent from using native exception ? Is it a mingw issue or a 'missing change' ? Do i miss something ? > I'm not sure if you can reliably throw native exceptions across DLLs though, > so even that might still not work, but you may want to try and see. I guess it might depend on the exception system used by the compiler... (sjlj...?) But that needs to be tested :-) thanks :-) Xavier _______________________________________________ Gnustep-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnustep-dev
