How are those warts? There's a lot of information in there. For XML, for example. the load.factor has had the order of loading modules changed many times when I reorganize the module. What if I counted every USING: or IN: line and declared that Factor had, say, 523 warts? There's nothing wrong with having a module system that requires that the programmer write stuff, as long as that stuff contains information.
On 1/19/07, Eduardo Cavazos <[EMAIL PROTECTED]> wrote: > Slava, > > Let's compare warts. :-) Before I mentioned that I don't care for load.factor > files as they do the job of a directory; indicate a set of files. > > The current module system has, let me see, > > find libs/ -name load.factor | wc -l ... > > 41 warts. ;-) > > How many lines are used in those loads? > > wc -l `find libs/ -name load.factor` ... > > 426 > > That's just the libs directory. For all modules, it's 78 files and 1126 lines. > > That's alot of overhead for an organization scheme. > > Ed > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Factor-talk mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/factor-talk > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
