• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSApplication terminate: behavior
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSApplication terminate: behavior


  • Subject: Re: NSApplication terminate: behavior
  • From: Andreas Färber <email@hidden>
  • Date: Fri, 20 Jan 2006 18:47:03 +0100

Hi John,

What do you want to do that you can't do in -applicationWillTerminate:?

I said so: I want both the managed runtime (Mono) to do a final, complete garbage collection run (shutdown) and native Cocoa to shut down in a normal way.


Right now either way it's only one of them that gets shut down correctly.

If I exit Mono in -applicationWillTerminate: then Mono exits fine, calling my managed finalizers, but Cocoa does not, as described, with the display not being updated for some time and the windows etc. not being removed.

It is simply not good behavior for native code to exit a managed Mono or whatever runtime through a call to exit(). How does Java handle this? Does it face the same problem or does it return to its main?

Andreas

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >NSApplication terminate: behavior (From: Andreas Färber <email@hidden>)
 >Re: NSApplication terminate: behavior (From: "John C. Randolph" <email@hidden>)

  • Prev by Date: Re: Weird problem with Core Data
  • Next by Date: Re: Weird problem with Core Data
  • Previous by thread: Re: NSApplication terminate: behavior
  • Next by thread: Re: NSApplication terminate: behavior
  • Index(es):
    • Date
    • Thread