Re: [AD] refactoring Allegro

[Jon Rafkind <workmin@xxxxxxxxxx>]

Grzegorz Adam Hankiewicz wrote:
> On 2006-08-20, Jon Rafkind <workmin@xxxxxxxxxx> wrote:
>   
>> Hi,
>>     I just made a new topic on allegro.cc asking people to help
>> refactor Allegro. My hope is the community will rewrite small
>> parts of Allegro and once a better version of the code is ready
>> it will be posted here for review and finally committed. Does
>> this sound like a reasonable project?
>>     
>
> If you are talking about 4.3, that's of no use. About 4.2, I would
> say it's cool, kind of the linux kernel janitor project, but cleanups
> could also introduce new bugs (or notice unseen bugs in current
> code). You probably won't get much people interested in a dead horse.
>
>   
Yea I meant 4.2. The other devs that replied in the allegro.cc thread
didnt seem overly enthusiastic about it, probably because its annoying
to manage changes to 4.2 and work on 4.3 at the same time. Thats a
reasonable greivance, and so maybe the code review can wait till 4.3
comes out. Either way I think it should be started at some point in
Allegro's lifetime.

Of course I wouldnt want any new bugs to pop up or any functions to slow
down so anything new would have to be heavily scrutinized. Maybe the
first step is to write a script that enforces the Allegro coding style
so at least that step doesnt have to be manually verified.