On 8 June 2012 14:22, Irek Szczesniak <[email protected]> wrote: > So unless ast-ksh starts shipping a 2nd kind of libcmd with grep, od, > tr, xargs included it may be better to just move them into libcmd for > ksh93u+. It can't be harmful.
I think a 2nd libcmd.so-alike will waste resources unless a significant amount of builtins is in there. Loading a shared library is expensive and consumes considerable machine resources. A server machine with 64GB memory might not care but a ARM miniserver (like those gumstik-alike machines with 512 sticks in a single 19' rack, representing 512 miniserver with 128MB each and a large etherswitch to connect them all) with only 128MB will suffer from that. Counting the size of the individual commands together I get ~100k, which is FAR below the 256k threshold at which the per-process overhead for a shared library can be justified on ARM: -rw-r--r-- 1 dan users 26784 Jun 8 16:18 grep.o -rw-r--r-- 1 dan users 42688 Jun 8 16:18 od.o -rw-r--r-- 1 dan users 13864 Jun 8 16:18 tr.o -rw-r--r-- 1 dan users 14472 Jun 8 16:18 xargs.o IMO it makes more sense to put these commands into libcmd.so, let it be for the ease of installation or resource usage. As a personal note, I do like the idea of putting these four commands into libcmd.so by default. It'll make things easier for programmers because it makes trusted versions of these commands available in all circumstances. _______________________________________________ ast-developers mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-developers
