[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Sat, 13 Jan 2001, Grzegorz Adam Hankiewicz wrote:
> Ah, yes, I forgot about that (too used to GFX_SAFE not failing :). But
> wouldn't it be better for GFX_SAFE to return with failure? The user
> program might have some unsaved data or opened files which need correct
> treatement before closing.
No, GFX_SAFE should continue to work as it has. The whole idea of
GFX_SAFE is that things are completely screwed up if it doesn't work. You
should not open and then not close files or anything like that before
using it.
It would be wrong for a programmer to use an API that, by the
documentation may not ever return, and have stuff in an incompletely
state.
It would be like using xmalloc in some critical code (xmalloc is a
non-standard function that exits the program if there is no memory
available).
> Grzegorz Adam Hankiewicz gradha@xxxxxxxxxx - http://gradha.infierno.org
> Other web pages: http://glub.ehu.es/ - http://welcome.to/gogosoftware/
>
>
--
The Phoenix -- The Artistic Intuition Company
Runica * Phoenix Quake * Caelius * Zen-X * Mirror Reflex * Infinite Realms