On Mon, 17 Mar 2008 12:51:14 -0700, [EMAIL PROTECTED] wrote:
On Mar 17, 12:15 pm, rockingred [EMAIL PROTECTED] wrote:
On Mar 10, 11:30 am, [EMAIL PROTECTED] [EMAIL PROTECTED]
Unfortunately, no free VC system existed for the language in which I
was programming
Explain? VC isn't
Marc 'BlackJack' Rintsch [EMAIL PROTECTED] writes:
[A general VCS] depends usually on the fact that there are
individual files. Preferably text files if you want automagic
merging of different changes.
Yes.
Now think of languages that are tightly coupled with their IDE
storing only binary
On Mar 9, 2:04 am, Ryan Ginstrom [EMAIL PROTECTED] wrote:
On Behalf Of Grant Edwards
I think docstrings are a great idea. What's needed is a way
to document the signature that can't get out-of-sync with
what the fucntion really expects.
Like doctests? (I know, smart-ass response)
On Mar 10, 11:30 am, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Fix that. That's usually something that's fairly easy to get done as
a programmer (I've had to do it at 2 of the last 4 places I worked).
Just go explain all the problems that can happen by not having VC and
all the benefits it
On Mar 17, 12:15 pm, rockingred [EMAIL PROTECTED] wrote:
On Mar 10, 11:30 am, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
Fix that. That's usually something that's fairly easy to get done as
a programmer (I've had to do it at 2 of the last 4 places I worked).
Just go explain all the
On Mar 10, 4:16 am, [EMAIL PROTECTED] wrote:
On Mar 9, 4:25 am, Lie [EMAIL PROTECTED] wrote:
On Mar 9, 3:27 am, [EMAIL PROTECTED] wrote:
To Lie:
Personally I preferred a code that has chosen good names but have
little or no comments compared to codes that makes bad names and have
On Mar 11, 11:31 am, Lie [EMAIL PROTECTED] wrote:
On Mar 10, 4:16 am, [EMAIL PROTECTED] wrote:
On Mar 9, 4:25 am, Lie [EMAIL PROTECTED] wrote:
On Mar 9, 3:27 am, [EMAIL PROTECTED] wrote:
To Lie:
Personally I preferred a code that has chosen good names but have
little or
On Mar 8, 8:27 pm, Dan Bishop [EMAIL PROTECTED] wrote:
// Copyright (C) 2008 Foobar Computer Consulting
//
// VERSION PROJECT# DATE DESCRIPTION
// --- --
// 1.00 123456 01/04/08 Original creation.
//
Eleven lines,
rockingred schreef:
On Mar 8, 8:27 pm, Dan Bishop [EMAIL PROTECTED] wrote:
//Copyright (C) 2008 Foobar Computer Consulting
//
//VERSION PROJECT# DATE DESCRIPTION
//--- --
// 1.00 12345601/04/08 Original
On Mar 10, 10:26 am, Roel Schroeven [EMAIL PROTECTED]
wrote:
rockingred schreef:
On Mar 8, 8:27 pm, Dan Bishop [EMAIL PROTECTED] wrote:
// Copyright (C) 2008 Foobar Computer Consulting
//
// VERSION PROJECT# DATE DESCRIPTION
// ---
On Mar 10, 11:30 am, rockingred [EMAIL PROTECTED] wrote:
On Mar 10, 10:26 am, Roel Schroeven [EMAIL PROTECTED]
wrote:
rockingred schreef:
On Mar 8, 8:27 pm, Dan Bishop [EMAIL PROTECTED] wrote:
//Copyright (C) 2008 Foobar Computer Consulting
//
//VERSION PROJECT#
On Mar 9, 3:27 am, [EMAIL PROTECTED] wrote:
To Lie:
Personally I preferred a code that has chosen good names but have
little or no comments compared to codes that makes bad names and have
Personally I don't. Show me a good one. Until you do, it's not that
I won't like it, it's that I
On Mar 8, 7:51 pm, Steven D'Aprano [EMAIL PROTECTED]
cybersource.com.au wrote:
On Sat, 08 Mar 2008 13:40:56 -0800, dave_mikesell wrote:
On Mar 8, 2:27 pm, [EMAIL PROTECTED] wrote:
Good comments are better than bad names. Good names are better than bad
comments.
If you're taking the time
On Mar 9, 4:25 am, Lie [EMAIL PROTECTED] wrote:
On Mar 9, 3:27 am, [EMAIL PROTECTED] wrote:
To Lie:
Personally I preferred a code that has chosen good names but have
little or no comments compared to codes that makes bad names and have
Personally I don't. Show me a good one. Until
Good comments are better than bad names. Good names are better than bad
comments.
If you're taking the time to write good comments, why not just fix the
bad names? The compiler/interpreter can never, ever catch bad comments.
Yes, but the Python compiler can only catch bad names if
On Fri, 07 Mar 2008 20:57:32 -0800, dave_mikesell wrote:
x = get_stuff(store) # Get the stuff what was brought at the store.
Perfect example of an unnecessary comment. The variable and function
names are commentary enough.
x is a terrible name. What does it mean? Nothing. There's only
On Mar 8, 2:38 am, Steven D'Aprano [EMAIL PROTECTED]
cybersource.com.au wrote:
On Fri, 07 Mar 2008 20:57:32 -0800, dave_mikesell wrote:
x = get_stuff(store) # Get the stuff what was brought at the store.
Perfect example of an unnecessary comment. The variable and function
names are
On 2008-03-08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
The function name also doesn't explain anything. How was the stuff got?
Was it paid for, or stolen, or picked up on consignment, or what? Compare
the above line with:
x = get_stuff(store) # Steal stuff from the store.
or
x =
On Mar 8, 9:31 am, Grant Edwards [EMAIL PROTECTED] wrote:
On 2008-03-08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
The function name also doesn't explain anything. How was the stuff got?
Was it paid for, or stolen, or picked up on consignment, or what? Compare
the above line with:
x =
Personally I preferred a code that has chosen good names but have
little or no comments compared to codes that makes bad names and have
twenty pages of comments to read and understand what it's about.
Personally, I think comments should be made as short and as concise as
possible and codes should
On 2008-03-08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Does one side of this hold that there are no -good- comments?
I wouldn't say there are _no_ good comments, but I would say
that 90+% of the comments I've seen in my lifetime were bad.
Most of them were bad to the extent that anybody new
On Mar 8, 1:31 pm, Grant Edwards [EMAIL PROTECTED] wrote:
On 2008-03-08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Does one side of this hold that there are no -good- comments?
I wouldn't say there are _no_ good comments, but I would say
that 90+% of the comments I've seen in my lifetime
What I really can't stand are the
pointy-haired comment blocks at the
beginnings of C/C++ functions that do
things like tell you the name and return
type of the function and list the names
and types of the parameters. Gee, thanks.
I never could have figured that out from
looking at
On Mar 8, 1:31 pm, Grant Edwards [EMAIL PROTECTED] wrote:
On 2008-03-08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Does one side of this hold that there are no -good- comments?
I wouldn't say there are _no_ good comments, but I would say
that 90+% of the comments I've seen in my lifetime
On Mar 8, 1:31 pm, Grant Edwards [EMAIL PROTECTED] wrote:
hilarious rant snipped
LOL. Thanks for the laughs. I share your frustration.
--
http://mail.python.org/mailman/listinfo/python-list
On Mar 8, 2:27 pm, [EMAIL PROTECTED] wrote:
Good comments are better than bad names.
Good names are better than bad comments.
If you're taking the time to write good comments, why not just fix the
bad names? The compiler/interpreter can never, ever catch bad
comments.
--
On 2008-03-08, K Viltersten [EMAIL PROTECTED] wrote:
What I really can't stand are the pointy-haired comment blocks
at the beginnings of C/C++ functions that do things like tell
you the name and return type of the function and list the
names and types of the parameters. Gee, thanks. I never
If you can't/don't look at the source file,
then comments aren't going to help (except
in the case of something like docstrings in
Python).
I strongly disagree. Now, perhaps we're
talking about different things, here?
Usually, in the header file (C++), there
won't be any source code,
On 2008-03-08, K Viltersten [EMAIL PROTECTED] wrote:
If you can't/don't look at the source file,
then comments aren't going to help (except
in the case of something like docstrings in
Python).
I strongly disagree. Now, perhaps we're
talking about different things, here?
Usually, in the
On Sat, 08 Mar 2008 19:31:47 +, Grant Edwards wrote:
I'm also a bit baffled by people who put a comment at the top of every
file that tells you what the filename is.
[snip rant]
You've never printed out a source file on pieces of dead tree to read on
the train on the way home, or in bed
On Sat, 08 Mar 2008 21:21:48 +0100, K Viltersten wrote:
Coming from C++/Java camp i can't help noticing that in most cases, when
i'm using a class written by somebody else, i don't want to see his/her
code. I only want to know WHAT the function does (is intended to be
doing, at least).
I
On Mar 8, 1:31 pm, Grant Edwards [EMAIL PROTECTED] wrote:
...
rant
What I really can't stand are the pointy-haired comment blocks
at the beginnings of C/C++ functions that do things like tell
you the name and return type of the function and list the names
and types of the parameters. Gee,
[EMAIL PROTECTED] writes:
On Mar 8, 2:38 am, Steven D'Aprano [EMAIL PROTECTED]
cybersource.com.au wrote:
On Fri, 07 Mar 2008 20:57:32 -0800, dave_mikesell wrote:
x = get_stuff(store) # Get the stuff what was brought at the store.
Perfect example of an unnecessary comment. The variable
If you can't/don't look at the source file,
then comments aren't going to help (except
in the case of something like docstrings in
Python).
I strongly disagree. Now, perhaps we're
talking about different things, here?
Usually, in the header file (C++), there
won't be any source code,
On Mar 8, 5:14 pm, K Viltersten [EMAIL PROTECTED] wrote:
/** Projects an object from 3D to 2D using
the method of Alexander The Great.
\param 3D structure to be projected
\returns 2D projection
*/
public Proj2D get2Dfrom3D(Proj3D param);
The above is, to me, very clear and
/** Projects an object from 3D to 2D using
the method of Alexander The Great.
\param 3D structure to be projected
\returns 2D projection
*/
public Proj2D get2Dfrom3D(Proj3D param);
The above is, to me, very clear and
consistent. Not to mention, easily
handled with e.g.
On Mar 8, 7:34 pm, Steven D'Aprano [EMAIL PROTECTED]
cybersource.com.au wrote:
On Sat, 08 Mar 2008 19:31:47 +, Grant Edwards wrote:
I'm also a bit baffled by people who put a comment at the top of every
file that tells you what the filename is.
[snip rant]
You've never printed out a
On Sat, 08 Mar 2008 20:45:25 -0800, [EMAIL PROTECTED] wrote:
On Mar 8, 7:34 pm, Steven D'Aprano [EMAIL PROTECTED]
cybersource.com.au wrote:
On Sat, 08 Mar 2008 19:31:47 +, Grant Edwards wrote:
I'm also a bit baffled by people who put a comment at the top of
every file that tells you
On 2008-03-08, K Viltersten [EMAIL PROTECTED] wrote:
If you can't/don't look at the source file,
then comments aren't going to help (except
in the case of something like docstrings in
Python).
I strongly disagree. Now, perhaps we're
talking about different things, here?
Usually, in the
On 2008-03-09, K Viltersten [EMAIL PROTECTED] wrote:
/** Projects an object from 3D to 2D using
the method of Alexander The Great.
\param 3D structure to be projected
\returns 2D projection
*/
public Proj2D get2Dfrom3D(Proj3D param);
The above is, to me, very clear and
On 2008-03-09, Steven D'Aprano [EMAIL PROTECTED] wrote:
On Sat, 08 Mar 2008 19:31:47 +, Grant Edwards wrote:
I'm also a bit baffled by people who put a comment at the top of every
file that tells you what the filename is.
[snip rant]
You've never printed out a source file on pieces of
On 2008-03-09, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Even in the early 1990s the moral equivalent of enscript (I think it
was a2ps)
I still use a2ps occasionally, but rarely for printing out
source code. I occasionally print out hex dumps that I need to
markup to figure out what's going
On 2008-03-09, Steven D'Aprano [EMAIL PROTECTED] wrote:
The only times I can recall printing source were in college
classes where I was required to hand in a hardcopy with the
assignment and code samples for job interviews. In the real
world the code base tends to be too huge to contemplate
On 2008-03-09, Steven D'Aprano [EMAIL PROTECTED] wrote:
On Sat, 08 Mar 2008 21:21:48 +0100, K Viltersten wrote:
Coming from C++/Java camp i can't help noticing that in most cases, when
i'm using a class written by somebody else, i don't want to see his/her
code. I only want to know WHAT the
On 2008-03-09, Dan Bishop [EMAIL PROTECTED] wrote:
On Mar 8, 1:31 pm, Grant Edwards [EMAIL PROTECTED] wrote:
...
rant
What I really can't stand are the pointy-haired comment blocks
at the beginnings of C/C++ functions that do things like tell
you the name and return type of the function and
On Sun, 09 Mar 2008 05:29:42 +, Grant Edwards wrote:
Sure, but really, adding ONE LINE to the start of a file is hardly
cluttering up anything. Especially if it is in the doc string, like
this:
widgets.py: create, manage and destroy widgets.
blah blah blah blah...
The bad part is
On Behalf Of Grant Edwards
I think docstrings are a great idea. What's needed is a way
to document the signature that can't get out-of-sync with
what the fucntion really expects.
Like doctests? (I know, smart-ass response)
Regards,
Ryan Ginstrom
--
On Mar 9, 12:09 am, Steven D'Aprano [EMAIL PROTECTED]
cybersource.com.au wrote:
On Sat, 08 Mar 2008 20:45:25 -0800, [EMAIL PROTECTED] wrote:
On Mar 8, 7:34 pm, Steven D'Aprano [EMAIL PROTECTED]
cybersource.com.au wrote:
On Sat, 08 Mar 2008 19:31:47 +, Grant Edwards wrote:
I'm also a
I've been recommended reading of:
http://www.python.org/dev/peps/pep-0008/
and in there i saw two things that i
need to get elaborated.
1. When writing English, Strunk and
White apply.
Where can i download it? Am i actually
expected to read the whole book? How
many people actually do aply it?
Placing 2 spaces after a period is standard, grammatically correct English,
at least as I was taught...
I don't know who Strunk or White are. Maybe Mr. Pink has a book you can
refer to instead.
2008/3/7, K Viltersten [EMAIL PROTECTED]:
I've been recommended reading of:
On Fri, Mar 7, 2008 at 4:31 PM, K Viltersten [EMAIL PROTECTED] wrote:
1. When writing English, Strunk and
White apply.
I apply Fowler, PEP 8 be damned. ;-)
--
Cheers,
Simon B.
[EMAIL PROTECTED]
http://www.brunningonline.net/simon/blog/
--
K Viltersten [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
1. When writing English, Strunk and White apply.
Do they? I've never seen them ;)
2. You should use two spaces after a sentence-ending period.
For heavens sake, why?
Most people find it easier to type two spaces than
On Fri, 7 Mar 2008 17:31:35 +0100
K Viltersten [EMAIL PROTECTED] wrote:
I've been recommended reading of:
http://www.python.org/dev/peps/pep-0008/
and in there i saw two things that i
need to get elaborated.
1. When writing English, Strunk and
White apply.
Where can i download it?
On Fri, 7 Mar 2008 16:44:10 +
Simon Brunning [EMAIL PROTECTED] wrote:
On Fri, Mar 7, 2008 at 4:31 PM, K Viltersten [EMAIL PROTECTED] wrote:
1. When writing English, Strunk and
White apply.
I apply Fowler, PEP 8 be damned. ;-)
Fowler's is good too but much more comprehensive.
K Viltersten wrote:
I've been recommended reading of:
http://www.python.org/dev/peps/pep-0008/
and in there i saw two things that i need to get elaborated.
1. When writing English, Strunk and White apply.
Where can i download it? Am i actually
expected to read the whole book?
It's a
On 2008-03-07, D'Arcy J.M. Cain [EMAIL PROTECTED] wrote:
2. You should use two spaces after a sentence-ending period.
For heavens sake, why? I've always been obstructed by the double
blanks but tolerated them. Now, that i read that it actually is a
recommendation, i need to ask about the
2. You should use two spaces after a
sentence-ending period.
For heavens sake, why? I've always been
obstructed by the double blanks but
tolerated them. Now, that i read that
it actually is a recommendation, i need
to ask about the purpose.
(a) It makes the ends of sentences more
On 2008-03-07, Jon Ribbens [EMAIL PROTECTED] wrote:
Personally, I dislike double spaces after sentences, but it is
not wrong to put them there any more than it is wrong not to
put them there.
You're lucky my high school typing teacher didn't hear you say
that...
--
Grant Edwards
Personally, I dislike double spaces after
sentences, but it is not wrong to put them
there any more than it is wrong not to put
them there.
You're lucky my high school typing teacher
didn't hear you say that...
I'm unclear if your teacher was a double or
single spacer. It's only
On 7 Mar 2008 17:40:08 GMT
Jon Ribbens [EMAIL PROTECTED] wrote:
Well, no, it's to follow a particular person's choice out of the many
and various competing rules of correct English usage. Personally,
I dislike double spaces after sentences, but it is not wrong to put
them there any more than
-On [20080307 19:10], D'Arcy J.M. Cain ([EMAIL PROTECTED]) wrote:
The arguments for one over the other fall into these basic ones. Use
double spaces to make the document easier to read, especially by people
who read a lot and tend to skim to absorb as much information as
possible. Use single
On 2008-03-07, K Viltersten [EMAIL PROTECTED] wrote:
Personally, I dislike double spaces after sentences, but it is
not wrong to put them there any more than it is wrong not to
put them there.
You're lucky my high school typing teacher didn't hear you say
that...
I'm unclear if your
On Fri, 07 Mar 2008 11:58:38 -0500, D'Arcy J.M. Cain wrote:
2. You should use two spaces after a
sentence-ending period.
For heavens sake, why? I've always been obstructed by the double blanks
but
tolerated them. Now, that i read that it actually is a recommendation,
i need to ask about
On 2008-03-07, Steven D'Aprano [EMAIL PROTECTED] wrote:
Professional typesetters, using proportional fonts, don't use double-
spaces because it throws off word spacing and line justification and just
plain looks ugly.
They do, however, put more space between sentences than they do
between
In article [EMAIL PROTECTED],
Grant Edwards [EMAIL PROTECTED] wrote:
My thumb has been putting two spaces after a period for 30
years, so the chances that it's going to change are rather
slim. :)
+1 QOTW
--
Aahz ([EMAIL PROTECTED]) * http://www.pythoncraft.com/
All problems
On Mar 7, 6:16 pm, Steven D'Aprano [EMAIL PROTECTED]
cybersource.com.au wrote:
I believe it is one of those things that everybody (for some value of
everybody) does because that's what they were taught to do
Actually I was never taught to, and I never learnt about it anywhere.
I started
to do
Grant Edwards grante Yow! A shapely CATHOLIC
at SCHOOLGIRL is FIDGETING
visi.com inside my costume..
... Are you wearing it? *plonkblock*
So, what gets you plonked around
K Viltersten [EMAIL PROTECTED] writes:
2. You should use two spaces after a sentence-ending period.
For heavens sake, why? I've always been obstructed by the double
blanks but tolerated them. Now, that i read that
it actually is a recommendation, i need to ask about the purpose.
AFAICT from
Grant Edwards [EMAIL PROTECTED] writes:
On 2008-03-07, Steven D'Aprano [EMAIL PROTECTED] wrote:
Professional typesetters, using proportional fonts, don't use double-
spaces because it throws off word spacing and line justification and just
plain looks ugly.
They do, however, put more
On Mar 7, 10:31 am, K Viltersten [EMAIL PROTECTED] wrote:
I've been recommended reading of:http://www.python.org/dev/peps/pep-0008/
and in there i saw two things that i
need to get elaborated.
1. When writing English, Strunk and
White apply.
If your code needs so much descriptive prose that
On Fri, 07 Mar 2008 20:04:47 -0800, dave_mikesell wrote:
On Mar 7, 10:31 am, K Viltersten [EMAIL PROTECTED] wrote:
I've been recommended reading
of:http://www.python.org/dev/peps/pep-0008/ and in there i saw two
things that i
need to get elaborated.
1. When writing English, Strunk and
On Mar 7, 10:38 pm, Steven D'Aprano [EMAIL PROTECTED]
cybersource.com.au wrote:
On Fri, 07 Mar 2008 20:04:47 -0800, dave_mikesell wrote:
On Mar 7, 10:31 am, K Viltersten [EMAIL PROTECTED] wrote:
I've been recommended reading
of:http://www.python.org/dev/peps/pep-0008/and in there i saw two
72 matches
Mail list logo
