logicchains / particlebench Goto Github PK

It looks like it's basically a straight line-by-line port of the C. A more idiomatic version would be using methods on structs. Would you accept a PR that updates this to be more sane?

Source code comments shouldn't be counted on the program size. Of course, the benchmark would need to parse each file knowing the language's comment syntax to remove them. But it is better than to force people to remove the comments of the source files themselves.

Other indicators like LOC or number of characters would be interesting, but maybe overwhelming. I'm just afraid that things like "public static final int, public static final int, public static final int" will compress too well. But of course, if I were to chose only one metric, the compressed size is better.

Not directly related, but it would also be interesting to know the executable file size, with notes if it requires external VMs and such or is standalone.

Why write:

Pts[i].VX += windX * 1 / Pts[i].R;

and not simply:

Pts[i].VX += windX / Pts[i].R;

(in all source files, and for Y and Z dimensions too)? It got me thinking about operator precedence... but of course it don't matters... :/