Re: [AD] END_OF_MAIN removal patch for msvc |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
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:
> > > On November 18, 2008, Peter Wang wrote:
> > > > We'd only run the user's code in a new thread if it's actually
> > > > necessary. That means Mac OS X, where we already do that.
> > >
> > > Why not make it consistent? If allegro has to fire off a thread /anyhow/
> > > might as well make it the same code.
> >
> > I have no real objection to that, except that al_run() should be
> > optional where possible. On the platforms where it's optional, Allegro
> > needs to be prepared to spawn a thread for itself anyway. It'd probably
> > be simpler to *always* do that on those platforms.
>
> No. Just like END_OF_MAIN it ISNT optional. (technically you can leave it out
> on some platforms, but then you end up with problems on others). al_run
> shouldn't be either. Its better to be consistent and require a certain api.
No. I may want to use Allegro in an environment where my code is not
allowed to block in al_run(). I know it might not work on certain
platforms, but that's my choice to make.
Peter