achates wrote:
> With spaces for indentation, this just isn't possible, because I have
> to conform to your viewing preferences, and that makes me unhappy. Why
> would you want to make me unhappy?
+5 QOTW
--
Edward Elliott
UC Berkeley School of Law (Boalt Hall)
complangpython at eddeye dot net
Xah Lee wrote:
> Tabs vs Spaces can be thought of as parameters vs hard-coded values, or
> HTML vs ascii format, or XML/CSS vs HTML 4, or structural vs visual, or
> semantic vs format. In these, it is always easy to convert from the
> former to the latter, but near impossible from the latter to the
Duncan Booth wrote:
>but I prefer editors which keep things
>simple. The tab key is particularly prone to excessively complicated
>actions, for example the editor I use has the following (not simple at
>all, and in fact not even an accurate description of what it does) binding
>for the tab key:
achates wrote:
> A tab is not equivalent to a number of spaces. It is a character
> signifying an indent, just like the newline character signifies the end
> of a line.
This link posted over in comp.lang.perl.misc expands on that:
http://numeromancer.dyndns.org/~timothy/tab-width-independence/de
[EMAIL PROTECTED] opalinski from opalpaweb wrote:
>>Simply put, tabs is proper, and spaces are improper.
>>Why? This may seem
>>ridiculously simple given the de facto ball of confusion: the semantics
>>of tabs is what indenting is about, while, using spaces to align code
>>is a hack.
>
>
> The r
Iain King wrote:
> Oh God, I agree with Xah Lee. Someone take me out behind the chemical
> sheds...
>
> Xah Lee wrote:
Please don't feed the troll!
And for the record, spaces are 100% portable, tabs are not. That ends
the argument for me.
Worse than either tabs or spaces however is Sun's mi
"[EMAIL PROTECTED] opalinski from opalpaweb" <[EMAIL PROTECTED]> writes:
>> Simply put, tabs is proper, and spaces are improper.
>> Why? This may seem
>> ridiculously simple given the de facto ball of confusion: the semantics
>> of tabs is what indenting is about, while, using spaces to align code
> Simply put, tabs is proper, and spaces are improper.
> Why? This may seem
> ridiculously simple given the de facto ball of confusion: the semantics
> of tabs is what indenting is about, while, using spaces to align code
> is a hack.
The reality of programming practice trumps original intent of t
Xah Lee wrote:
> Tabs versus Spaces in Source Code
>
> Xah Lee, 2006-05-13
>
> In coding a computer program, there's often the choices of tabs or
> spaces for code indentation. There is a large amount of confusion about
> which is better. It has become what's
An old debate. My $0.02 :
http://numeromancer.dyndns.org/~timothy/tab-width-independence/description.html
The idea can be extended to other programming languages.
TS
--
http://mail.python.org/mailman/listinfo/python-list
Duncan Booth enlightened us with:
> It could be, and for some keys (q, w, e, r, t, y, etc. spring to
> mind) that is quite a reasonable implementation. For others 'tab',
> 'backspace', 'enter', 'delete', etc. it is less reasonable, but it
> is a quality of implementation issue. If I had an editor w
Sybren Stuvel wrote:
>> An editor should be capable of letting you create or modify files
>> containing control characters without gratuitously corrupting them,
>> but the keys should perform the expected operations
>
> I agree with that.
>
>> not insert the characters.
>
> But not with that, s
Oh God, I agree with Xah Lee. Someone take me out behind the chemical
sheds...
Iain
Xah Lee wrote:
> Tabs versus Spaces in Source Code
>
> Xah Lee, 2006-05-13
>
> In coding a computer program, there's often the choices of tabs or
> spaces for code indentation. The
Duncan Booth enlightened us with:
> That is true so far as it goes, but equally if your editor inserts a
> tab character when you press the tab key it is as broken as though
> it inserted a backspace character when you press the backspace key.
> In both of these cases you have an operation (move to
On 5/15/06, Brian Quinlan <[EMAIL PROTECTED]> wrote:
> The problem with tabs is that people use tabs for alignment e.g.
>
> def foo():
>->query = """SELECT *
>-> -> -> FROM sometable
>-> -> -> WHERE condition"""
>
> Now I change my editor to use 8-space tabs and the code is all
achates wrote:
> A tab is not equivalent to a number of spaces. It is a character
> signifying an indent, just like the newline character signifies the end
> of a line. If your editor automatically converts tabs to spaces (i.e.
> you are unable to create source files containing tabs) then either i
Harry George wrote:
> The reason is simple: People get confused, and accidentally get the
> wrong tab indents when they move among editors or among settings on
> the same editor.
People certainly do get confused. I'm always amazed that so many
people, even amongst those who manage to make a livin
On 5/15/06, Edward Elliott <[EMAIL PROTECTED]> wrote:
> If such tools are lacking, use substitutes in the meantime. Don't allow any
> code to be checked in where a line departs more than one tab indentation
> level from its neighbors. It's not perfect, but it eliminates the worst
> offenses. Go
Brian Quinlan wrote:
> The problem with tabs is that people use tabs for alignment e.g.
>
> def foo():
>->query = """SELECT *
>-> -> -> FROM sometable
>-> -> -> WHERE condition"""
Sure it's a problem. When programmers do bad things, what is your response?
Slap his nose and
Peter Decker wrote:
> Funny, I was going to say that the problem is when the author prefers
> a font with a differntly-sized space. Some of us got rid of editing in
> fixed-width fonts when we left Fortran.
Don't know what all of the hub-bub here is regarding tab/space
indentation. My punched car
On 5/15/06, Brian Quinlan <[EMAIL PROTECTED]> wrote:
> The problem with tabs is that people use tabs for alignment e.g.
>
> def foo():
>->query = """SELECT *
>-> -> -> FROM sometable
>-> -> -> WHERE condition"""
>
> Now I change my editor to use 8-space tabs and the code is all
Edward Elliott wrote:
> Tab is not 4 spaces. Tab is 1 level of indentation. The confusion that
> tabs equals some fixed width, or can/should be set to some fixed width, is
> the entire problem hampering their use. It implies that conversion between
> tabs and spaces is straightforward when it is
Harry George wrote:
> This has been discussed repeatedly, and the answer is "If you only
> work alone, never use anyone else's code and no one ever uses your
> codes, then do as you please.
The answer is "Do what works best for your project". Smart people can agree
on and use whatever conventio
On 5/15/06, Chris Klaiber <[EMAIL PROTECTED]> wrote:
> The problem comes when the author prefers a smaller tab width than what my
> editor is set to. Sure, I could change it for that file, but what if I'm
> reading a whole directory? Sure, I could change the default setting in my
> editor, but wha
Edward Elliott <[EMAIL PROTECTED]> writes:
> Eli Gottlieb wrote:
>
> > Actually, spaces are better for indenting code. The exact amount of
> > space taken up by one space character will always (or at least tend to
> > be) the same, while every combination of keyboard driver, operating
> > system
Xah Lee wrote:
> Tabs versus Spaces in Source Code
>
> Xah Lee, 2006-05-13
>
> In coding a computer program, there's often the choices of tabs or
> spaces for code indentation. There is a large amount of confusion about
> which is better. It has become what's
I agree, use tabs.
--
http://mail.python.org/mailman/listinfo/python-list
If I work on your project, I follow the coding and style standards you
specify.
Likewise if you work on my project you follow the established standards.
Fortunately for you, I am fairly liberal on such matters.
I like to see 4 spaces for indentation. If you use tabs, that's what I
will see,
Spaces work better. Hitting the TAB key in my Emacs will auto-indent
the current line. Only spaces will be used for fill. The worst thing
you can do is mix the two regardless of how you feel about tab vs
space.
The next step in evil is to give tab actual significance like in
make.
Xah Lee is g
On 5/14/06, Edward Elliott <[EMAIL PROTECTED]> wrote:
Eli Gottlieb wrote:> Actually, spaces are better for indenting code. The exact amount of> space taken up by one space character will always (or at least tend to> be) the same, while every combination of keyboard driver, operating
> system, text
Personally, I don't think it matters whether you use tabs or spaces for
code indentation. As long as you are consistent and do not mix the two.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
http://mail.python.org/mailman/li
Eli Gottlieb wrote:
> Actually, spaces are better for indenting code. The exact amount of
> space taken up by one space character will always (or at least tend to
> be) the same, while every combination of keyboard driver, operating
> system, text editor, content/file format, and character encodi
Actually, spaces are better for indenting code. The exact amount of
space taken up by one space character will always (or at least tend to
be) the same, while every combination of keyboard driver, operating
system, text editor, content/file format, and character encoding all
change precisely w
Xah Lee wrote:
> Tabs versus Spaces in Source Code
>
> Xah Lee, 2006-05-13
>
> In coding a computer program, there's often the choices of tabs or
> spaces for code indentation. There is a large amount of confusion about
> which is better. It has become what's
Tabs versus Spaces in Source Code
Xah Lee, 2006-05-13
In coding a computer program, there's often the choices of tabs or
spaces for code indentation. There is a large amount of confusion about
which is better. It has become what's known as “religious war” —
a heated fight over trivi
101 - 135 of 135 matches
Mail list logo
