Re: [AD] END_OF_MAIN removal patch for msvc

[Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx>]

On November 18, 2008, Peter Wang wrote:
> On 2008-11-18, Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx> wrote:
> > On November 18, 2008, Peter Wang wrote:
> > > On 2008-11-18, Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx> wrote:
> > > > Wait, didn't allegro specifically go to an event loop and whatnot to
> > > > get around this little problem? al_init() initializes any internal
> > > > lib state, and the event loop gives allegro time to "do its thing"
> > > > when needed without having an explicit al_update_allegro(); api.
> > >
> > > No, that's not what the event system was designed for and that's not
> > > how it works.
> >
> > Probably not.
> >
> > So whats the alternative then? Try and be too clever? or just export a
> > simple update function?
> >
> > What do you prefer?
>
> I prefer to wait for Apple to fix their stupid library.  Failing that, I
> proposed an improved END_OF_MAIN-like solution earlier in the thread.
> An update/polling function is even worse for creating code that won't
> port easily to Mac OS X.

How would it be worse for creating code? That whole ucontext stuff, and 
stealing the main thread thing is just asking for trouble. So is renaming 
main, or redirecting WinMain to main etc...

Its all a huge huge hack, and we don't need to do it. Just need the right api 
design to work on all major platforms WITHOUT massive ugly hacks.

> Peter
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge Build the coolest Linux based applications with Moblin SDK & win
> great prizes Grand prize is a trip for two to an Open Source event anywhere
> in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/


-- 
Thomas Fjellstrom
tfjellstrom@xxxxxxxxxx