4 ms·
The paper uses wc -l (probably because sloccount doesn't handle go and scala?) to count the lines of code. Here is the output of sloccount: SLOC Direct
by mulander 15y ago
The paper uses wc -l (probably because sloccount doesn't handle go and scala?) to count the lines of code.
Here is the output of sloccount:
SLOC Directory SLOC-by-Language (Sorted)
595 java_pro java=595
591 java java=591
488 cpp cpp=488
328 python python=328
0 go (none)
0 go_pro (none)
0 scala (none)
0 scala_pro (none)
generated using David A. Wheeler's 'SLOCCount'.
Compare it to the paper.
Benchmark wc -l
C++ Dbg/Opt 850
Java 1068
Java Pro 1240
Scala 658
Scala Pro 297
Go 902
Go Pro 786
- igouy 15y agoHere are GZip minimally compressed source-code sizes after removal of comments and removal of duplicate whitespace characters - Benchmark GZ Bytes Factor (wc -l Factor from paper) Java Pro 5198 1.65x 1.9x Java 4403 1.40x 1.6x C++ 4229 1.34x 1.3x Go 3768 1.20x 1.4x Go Pro 3259 1.03x 1.2x Scala 3138 ==== === Python 2755 0.87x ???? Scala Pro 1929 0.61x 0.5x
- lbolla 15y agoThis is the result using cloc: Bench files blank comment code cpp 4 145 236 501 go 5 153 239 546 go_pro 5 132 233 457 java 8 151 352 605 java_pro 8 157 351 772 python 2 110 204 334 scala 2 104 224 384 scala_pro 2 59 62 230