On Fri, Aug 01, 2003 at 11:31:38PM +0200, Grzegorz wrote: [snip] > [1] - take the modules for instance. If saving ram would be such a high > priority, then it should be possible to load FvwmButtons and then use it > to create more than one container, perhaps in different areas of the > screen. But no, if you want two containers you need to load two copies > of FvwmButtons, even if 80% of that code could probably be shared (only > config-related data is different).
What is the problem with starting the same module twice? All you waste is a few hundred bytes of dynamic memory that could be shared by different containers, namely the memory used to store the constant parts of the configuration. And of course the two additional pipes and the process structure in the kernel. The executable itself is loaded into RAM only once. Any decent kernel is clever enough not to load multiple copies of the same write-only data. > And fvwm modules are quite big already. Try $ make install-strip Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
