RE: [AD] Discussion on Allegro 4.2 on allegro.cc

["Robert Ohannessian" <ROhannessian@xxxxxxxxxx>]

I agree with Shawn's point of getting it right the first time (ie:
breaking it only once). However, this is clearly an unworkable solution
for large OSS with few active developers.

Having two APIs simultaneously for the same module is not always
possible or workable. Doing it one function at has lot of issues
associated with it: it's hard to guess interactions with future (newer)
changes to other related functions.

I don't really have any good ideas for this one.




> -----Original Message-----
> From: alleg-developers-admin@xxxxxxxxxx [mailto:alleg-
> developers-admin@xxxxxxxxxx] On Behalf Of Evert Glebbeek
> Sent: Wednesday, August 04, 2004 12:31 AM
> To: alleg-developers@xxxxxxxxxx
> Subject: [AD] Discussion on Allegro 4.2 on allegro.cc
> 
> Allegro 4.2 has been discussed somewhat on this thread on Allegro.cc
for
> those who've missed it:
> http://www.allegro.cc/forums/view_thread.php?_id=390926#target
> I don't think quoting it all here is that useful.
> As Peter said:
> > I'd really like to get especially Eric, Angelo and Bob's responses.
> 
> Evert
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes
on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source
Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers