Re: Talking about the GUI

* Ronald Bultje <[email protected]> [2004-01-16 10:24:46 +0100]:

<snip>
> You have needs for a subset of glib. So does everyone else (I don't
> believe there's a single person out there using all functions & features
> in glib). If you break down glib in small pieces so everyone can link to
> the combination of modules that brings the needed code into his app and
> doesn't link to unneeded code, how much do you think dynamic library
> overhead would be?

Yes. 
The glib itself should be splitted off into several small modules.
Each of these modules must have consistent interfaces and dependencies.
For example the core module would only handle primitive memory and module
handling. Other functionality, i.e. containter datatypes or filesystem, 
sits on top of that.

If we divide library vs. module from the first steps and declare a library 
as a container for modules, then its the job of the buildsystem to define
how evrything is linked together (i.e. putting multiple very small modules 
into one library to save memory which otherwise would be wasted because
of the page boundary)


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT services

  phone:     +49 36207 519931         www:       http://www.metux.de/
  fax:       +49 36207 519932         email:     [email protected]
  cellphone: +49 174 7066481
---------------------------------------------------------------------
 Diese Mail wurde mit UUCP versandt.      http://www.metux.de/uucp/