Re: [AD] got rid of END_OF_MAIN()

[Michael Benfield <leftfist@xxxxxxxxxx>]

>    Doesn't anyone think that any preprocessor stuff at all is wrong? 
> The
> proper way to get rid of END_OF_MAIN is to have a mandatory alleg_init
> -like function which does what the current main wrapper does. Having
> the main() function in liballegro instead of the main binary is just
> as ugly; if you want to see how to get rid of END_OF_MAIN while still
> having main() in the binary, see my patch from last week about the very
> same subject.

Trust me I agree with you 110%. In fact I don't think there's a need 
for another alleg_init like function - that functionality could just 
happen under the same function. But the way the OS X stuff is 
implemented there really is no way around it right now. No way around 
it that's not ugly anyway. I plan to try to figure out how to fix it. 
But it will not be trivial, considering I don't know the first thing 
about Cocoa.

I just meant this patch as a first step, I definitely want to try to 
get rid of all the main mangling nonsense entirely (although from the 
way people were talking before, they seem to want to keep main mangled 
under Windows so that programs can use WinMain... I don't see why 
though if main is a valid way to do it for Windows).

By the way, if anyone who DOES know Cocoa can point me in the right 
direction about how to get the Cocoa stuff running without taking over 
the main thread, please do.

Mike Benfield