Re: [COFF] Was [TUHS] tabs vs spaces - entab, detab

John P. Linderman wrote in <CAC0cEp9GVsYbjYhsYk2Hjjj90FxYFAia2Luy_vg854NTrV3Hww(a)mail.gmail.com>: |The tab/detab horse was still twitching, so I decided to beat it a little |more. | |Doug's claim that tabs saving space was an urban legend didn't ring true, |but betting again Doug is a good way to get poor quick. So I tossed |together a perl script (version run through col -x is at the end of this |note) to measure savings. A simpler script just counted tabs, |distinguishing leading tabs, which I expected to be very common, from |embedded tabs, which I expected to be rare. In retrospect, embedded tabs |are common in (my) C code, separating structure types from the element |names and trailing comments. As Norman pointed out, genuine tabs often |preserve line to line alignment in the presence of small changes. So the |fancier script distinguishes between leading tabs and embedded tabs for |various possible tab stops. Small tab stops keep heavily indented code |lines short, large tab stops can save more space when tabbing past leading |blanks. My coding style uses "set-width" of 4, which vi turns into spaces |or tabs, with "standard" tabs every 8 columns. My code therefore benefits |most with tabstops every 4 columns. A lot of code is indented 4 spaces, |which saves 3 bytes when replaced by a tab, but there is no saving with |tabstops at 8. Here's the output when run on itself (before it was |detabbed) and on a largish C program: | | /home/jpl/bin/tabsave.pl /home/jpl/bin/tabsave.pl rsort.c |/home/jpl/bin/tabsave.pl, size 1876 | 2: Leading 202, Embedded 3, Total 205 | 4: Leading 303, Embedded 4, Total 307 | 8: Leading 238, Embedded 5, Total 243 | |rsort.c, size 209597 | 2: Leading 13186, Embedded 4219, Total 17405 | 4: Leading 19776, Embedded 5990, Total 25766 | 8: Leading 16506, Embedded 6800, Total 23306 | |The bytes saved by using tabs compared to the (detabbed) original size are |not chump change, with 2, 4 or 8 column tabstops. On ordinary text, savings |are totally unimpressive, usually 0. Your savings may vary. I think the |horse is now officially deceased. -- jpl Not really. I mean, i do not insist of this, but i looked at the numbers. And despite col(1) 2.36.2 giving the wrong line when failing to dig a LATIN1 in UTF-8 (should be 7, gave 11), when i sum up the total of 8: in an old project with tests, documentation etc. here the output is 1044401. This is without generated data. I mean, even today i strip whitespace in shipout code, of generated data, of documentation parsed through processors. This includes mangling of internal interface headers and removal of their documentation and comments, but copyright. You know, only this automatized pre-release step of the pretty small open source MUA i maintain causes this line count change: 37 files changed, 2441 insertions(+), 10537 deletions(-) --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)