[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Sat, 2005-01-22 at 23:15 +0100, Evert Glebbeek wrote:
> Hmm... I don't like adding the al_ prefix for the 4.2 branch, since it's
> inconsistent with the rest of the library.
> I checked for font addons that defined a load_font, and the only one I
> could find that did was AllegTTF, which isn't going to work with the new
> FONT vtable anyway (I'll just send a message to the author though... he
> may want to update the library so that it remains compatible).
> I think this is really merging functionality that was in addons into the
> core library, where it belongs. So IMO, the addons should just be
> updated...
> That said, maybe we could add one of Allegro's tried-and-trusted
> preprocessor directives so that Allegro's load_font() can be renamed to
> al_load_font() if the user so wishes? I really don't want to make this the
> default though...
Well, I guess we can leave load_font. Just noticed before how it breaks
e.g. ASE, and with all the backwards compatibility things going on.. but
then, the same would be true for any newly introduced symbol since 4.0.0
- so yeah, nothing much we can do.
--
Elias Pschernig