RE: [AD] Five patches |
[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]
> i don't have the original mail so i can't check what exactly
> the patches did,
> but to answer you; the current feature-freeze only means new
> features aren't
> accepted. patches which cleans up or fixes broken features,
> just badly coded
> stuff or otherwise unreliable pieces of code ARE accepted. in
> other words, if
> this patch bugfixes, improves or completes an already
> existing feature it
> should be included.
It did not fix stuff, merely make conversion stuff more usable by
having a pool of conversion buffers, freeing one from having to
declare those nasty variables named tmp1, tmp2, tmp3 etc just for
unicode<->ascii conversion, and frees them all automatically when
the pool is freed. So it can be argued to be a feature, though it
makes life much easier. Allegro itself was not converted to use
it internally though, so it can't break. IIRC, just one example
program was modified to show how to use the buffer pool.
--
Vincent Penquerc'h
Mail converted by MHonArc 2.6.19+ | http://listengine.tuxfamily.org/ |