What's up, BYOND!
I personally don't like to condense my codes because the readability of it goes down and I tend to have a hard time pinpointing bugs, etc.
Feel free to write the reason why you do or don't condense your code!
ID:1265750
![]() May 16 2013, 8:16 am
|
|
![]() May 16 2013, 8:20 am
|
|
It depends.
|
If we're talking purely stylistically, I dunno why you would. It seems in most regards counter-productive, for the reasons you've stated. Harms readability, makes maintenance and debugging a bit trickier because of it, etc.
|
When we talk condensing, are we talking,
mob |
Kaiochao pretty much hit the nail on the head with his examples, thanks. I was also told that some people condense for shorter compile times? Is there any truth to this?
|
Not really, no. Condensing your code almost never matters in languages that gets compiled down to machine/byte-code and thrown in a binary. The only time condensing especially matters (though you'd use a tool to do this during deployment, rather than condensing it as you write it) is in the case of web programming, such as JavaScript. Helps cut down on page load times and bandwidth usage.
|
I condense my code once I've actually finished tinkering with it. Other than that, while I'm debugging and working on it, I keep everything nice and spaced out. I honestly don't mind if I do have to pick back through condensed code, however. I can read it just fine because I keep my code well documented and know what's going on where.
|
Personal preference. It might not be logical to you, but it works wonderfully for me.
|
Well no, quite. It's also not logical to the software community at large though, which is a bit more concerning perhaps.
|
I was meaning particularly for DM, though. When working with C++, I stick with a more standard format.
|
Got an example of what you mean by 'condense' for DM, out of curiosity? Maybe what I'm thinking, and what you're doing, are two quite different things. P:
|
getTarget() Basically I just mean removing all of the white space. |