It's kind of ironic that you didn't split that big chunk of text into
paragraphs, don't you think? ;)
Anyway, yes, I was referring to visual space, we all know that is more
clear the more you can see the code, that's why we don't let rows go
insinely long (well, wide actually), and that also applies for the
"vertical viewport" (rows also, not only columns) That's why *I* find
it a waste of (vertical) space.
But, as we all know also, coding style is just that, a style, yet
another matter of taste --of course, there are some basics that should
always be present for the sake of clarity (such as indentation,
comments, and an empty line here and there as logic-separator), or
that's what I think, anyway --let's not discuss about this, wi'l ya?
Paul Novitski wrote:
IMHO, vertical aligned brackets can be messy when nesting
relatively-small blocks (and seems to me like a lot of wasted space)
I'm struggling to get my head around this concept of 'wasted space' with
regard to software code. What is it that's getting wasted, exactly? If
we printed our programs on paper it would be wasted trees (page-space)
but I almost never do this and I don't know anyone who does except
banks. It could be seen as a waste of disk space, but only at the rate
of a few bytes per code block, carriage return plus perhaps a couple of
tabs. What we must be talking about here is a waste of visual space.
How does visual space get wasted? Isn't it possible to waste something
only if it's in finite supply? I guess it's being wasted if it's
something valuable that's not being used. However, the urge to add
whitespace to spread things apart is done with the intent of making code
easier to read, so that seems like a use, not a waste.
OK, OK, I'll stop. Think I'll go out and get wasted~
P.
--
Atentamente,
J. Rafael Salazar Magaña
Innox - Innovación Inteligente
Tel: +52 (33) 3615 5348 ext. 205 / 01 800 2-SOFTWARE
http://www.innox.com.mx
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
