Re: [AD] Allegro plug-in system (was: Is there a licensing reason why PNG isn't built-in to Allegro?)

[ Thread Index | Date Index | More lists.liballeg.org/allegro-developers Archives ]


The DLL hell is so bad mainly because the DLLs may get out of sync
easily, breaking API and ABI compatibility. Sometimes programmers don't
see that and the programs run strangelly, bugged, crashing randomly, or
misteriously won't compile giving away spurious errors deep inside
libraries. Worse, is possible to create programs which relies in some
bugs introduced by the DLL hell. This is even worser to novices.

As an example. Imagine if someone is building a game with Allegro-core
DLL 4.3.5, however using AllegroBMP DLL 4.3.3 and AllegroWAV DLL 4.3.6,
things will not work. If the user recompile each DLL, but for some
reason forget to recompile one or recompile to a different version, we
will get a DLL hell.

Victor Williams Stafusa da Silva

--- Elias Pschernig <elias@xxxxxxxxxx> wrote:

> On Sat, 2006-03-25 at 19:43 -0300, Victor wrote:
> > So we should get a plug-in system which comes with the standard
> > plug-ins plugged on by default, so newbies won't need to struggle
> on
> > how plug everything together. The experienced users could turn them
> > on/off easily.
> > 
> > About the DLL hell, we should think a way to workaround this. I
> have
> > seven ideas:
> > 
> 
> If "DLL hell" is so bad, why do we provide modules under unix even
> now?
> I think this always should stay as option.
> 
> The option to build everysthing static also should stay, I like it if
> you can create a single huge .exe :)
> 
> Building just one DLL probably isn't hard either, just need a
> plugin-aware mechanism in the build process.
> 
> -- 
> Elias Pschernig


		
_______________________________________________________ 
Novo Yahoo! Messenger com voz: Instale agora e faça ligações de graça. 
http://br.messenger.yahoo.com/




Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/