How about internally renaming mono_thread_manage and add a no-op version of it.
It would retain compatibility with wine and would not further complicate the shutdown sequence. This assumes that there's no good use case for calling the two independently. -- Rodrigo On Wed, Sep 10, 2014 at 5:58 PM, Vincent Povirk <madewokh...@gmail.com> wrote: > > 2. Should Mono be fixed to account for what I was doing? I'd prefer to > > have code that is as version-independent as possible. Maybe mono could > > somehow detect that mono_thread_manage was already completed by the > > current thread, and do nothing in this case? > > I wrote a patch using this approach: > > https://github.com/madewokherd/mono/commit/7baf38fd134f92f7d80f43bb3cf6d77122b3eb1e > > But I'm really not sure about this. >
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
