= 27d567bc2d48d9f40e9ccc20ea370b15)
Luke_A_Somers comments on Open thread, January 25- February 1 - Less Wrong Discussion
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (316)
It depends on your language and coding style, doesn't it? I've seen C style guides that require you to stretch out onto 15 lines what I'd hope to take 4, and in a good functional language shouldn't take more than 2.
Yes, and the number of lines is a ridiculously bad metric of the code's complexity anyway.
Was a funny moment when someone I know was doing a Java assignment, I got curious, and it turned out that a full page of Java code is three lines in Perl :-)
That really depends on coding style, again. I find that common Java coding styles are hideously decompressed, and become far more readable if you do a few things per line instead of maybe half a thing. Even they aren't as bad as the worst C coding styles I've seen, though, where it takes like 7 lines to declare a function.
As for Perl vs Java... was it solved in Perl by a Regex? That's one case where if you don't know what you're doing, Java can end up really bloated but it usually doesn't need to be all that bad.
I don't remember the details by now, but I think that yes, there was a regexp and a map, and a few of Perl's shortcuts turned out to be useful...