Re: [AD] Renamed API second draft |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: "Allegro Conductors" <conductors@xxxxxxxxxx>
- Subject: Re: [AD] Renamed API second draft
- From: xaviergonz@xxxxxxxxxx
- Date: Fri, 21 Dec 2001 23:30:33 +0100
- Wrom: AFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVT
> Here's my proposition:
> - general initialization: al_install_allegro()/al_remove_allegro()
functions
> with two macros allegro_init()/allegro_exit(). We could add a new
parameter
> to al_install_allegro():
allegro_exit() as macro for al_remove_allegro()? what kind of
parameters do al_remove_allegro() need? =)
I don't like the idea of mixing al_ allegro_ prefixes
we could have
al_initialize() or al_init() // like old install_allegro
al_initialize_default() or al_init_default() // old allegro_init
and allegro_deinitialize() or al_deinit() // we just need one function (like
old allegro) to deinit everything