On Thu, Apr 19, 2012 at 10:15 PM, Devin Jeanpierre
wrote:
> Why don't you allow nested multiline comments? Many languages (e.g.
> ML, Scheme, Haskell, etc.) allow you to nest multi-line comments. It's
> mostly the C family of languages that refuse to do this, AFAIK.
Allo
;
> Does Python need multi-line code removal? And if so, will something
> like this work?
Two questions:
Why don't you allow nested multiline comments? Many languages (e.g.
ML, Scheme, Haskell, etc.) allow you to nest multi-line comments. It's
mostly the C family of languages t
On Thu, Apr 19, 2012 at 8:17 PM, Alek Storm wrote:
>> comment def
>> ... parser completely ignores these lines ...
>> comment break
>
>
> I believe the more Pythonic syntax would be:
>
> comment:
> ...some
> ...indented
> ...lines
>
> God help us if that ever happens.
Certainly not. T
Chris Angelico wrote:
[snip]
Since Python doesn't have multiline comments, triple-quoted strings
are sometimes pressed into service. [snip]
Chris Angelico
Let the triple quotes where they're meant to be. Use your text editor,
any decent one will allow you to comment uncomment
use there's
> nowhere for it to "go". It's a special feature of the parser that
> takes a pile of text and stores it somewhere for self-documentation
> purposes.
>
> > Sorry, he's made a misparsed program (not parsed as he intended) by
> > using a strin
feature of the parser that
takes a pile of text and stores it somewhere for self-documentation
purposes.
> Sorry, he's made a misparsed program (not parsed as he intended) by
> using a string where he should have used a comment? And because of this
> he says we need (or should w
comment (were it a multiline
| > comment) can't disappear off my screen.
| >
| > I would say you've made a case _against_ multiline coments.
|
| On the contrary, he has definitely made a case for multiline comments.
Sorry, he's made a misparsed program (not parsed as he intended
kers, and the beginning and end of the comment (were it a multiline
> comment) can't disappear off my screen.
>
> I would say you've made a case _against_ multiline coments.
On the contrary, he has definitely made a case for multiline comments.
You just happen to disagree, and
On Thu, Apr 19, 2012 at 12:29 AM, Cameron Simpson wrote:
> I'd just do this:
>
> list = [
> Object1(arg),
> ## Object2(arg),
> ## Object3(arg),
> Object4(arg)
> ]
>
> Multiple lines of single line comments. Frankly, I find this much easier
> to see (all the disabled lines are delineated with
string.
You are aware that a string is not a comment?
| This caused a string to be appended to
| the list instead of ignoring the section. Consider the following code:
|
| list = [
| Object1(arg),
| """
| Object2(arg),
| Object3(arg),
| """
| Object4(arg)
| ]
|
|
the list instead of ignoring the section. Consider the following code:
list = [
Object1(arg),
"""
Object2(arg),
Object3(arg),
"""
Object4(arg)
]
Real multiline comments would produce [Object1, Object4]. The list, in
fact, contains [Object1, "Object2, Object3",
Sion Arrowsmith wrote:
> It appears to me that our fundamental difference is that you see value
> in long-term preservation of sections of commented-out code without
> any kind of real comment as to what's going on, whereas I consider
> this to be appallingly bad practice.
Then you're reading too
Edward Elliott <[EMAIL PROTECTED]> wrote:
>Sion Arrowsmith wrote:
>> Really? Under what circumstances is it easier to see what's going on
>> with start/end comments than with comment-to-end-of-line?
>Off the top of my head:
> [ ... ]
It appears to me that our fundamental difference is that you se
"OKB (not okblacke)" <[EMAIL PROTECTED]> writes:
> Ben Finney wrote:
> > If your revision control system is so inconvenient to use that
> > you'd rather have large blocks of commented-out code, it's time to
> > start using a better RCS -- perhaps a distributed one, so you can
> > commit to your ow
Ben Finney wrote:
> Indeed. Using revision control means never needing to comment out
> blocks of code.
>
> If your revision control system is so inconvenient to use that you'd
> rather have large blocks of commented-out code, it's time to start
> using a better RCS -- perhaps a distributed one,
rx wrote:
> Still a little strange to newcomers that there are three ways to do the
> same and that you should be carefull to use the right '''/""" inside the
> comment else the comment will not work for some reason.
>
> #comment
>
> '''
> comment
> '''
>
> """
> comment
> """
Please, note tha
"Jorge Godoy" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> rx wrote:
>
>> I don't understand the problem - why should comments (and I hope you
>> believe there should be a one line comment at least) be restricted to one
>> line. It doesn't work that way for if, while, for.
>
> It
>
> Of course! You should have used """ since you already used ''' in your
> triple-quoted text. But I'm just repeating what I already said (and kept
> above so that you can see it again).
>
> --
> Jorge Godoy <[EMAIL PROTECTED]>
>
Sorry - I should have read more carefully.
I like the ide
rx wrote:
> I don't understand the problem - why should comments (and I hope you
> believe there should be a one line comment at least) be restricted to one
> line. It doesn't work that way for if, while, for.
It is the minimum case that can solve a problem commenting one line -- or
part of it as
"Jorge Godoy" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> rx wrote:
>
>> I have commented out a lot of C++ code and miss the block feature in
>> python more than I missed the nested comments in C++.
>> Besides nothing really strange happened.
>> Sometimes you just need to diss
rx wrote:
>
> "Jorge Godoy" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>> Edward Elliott wrote:
>>
>
>>
>> You can use either """ or '''. I don't keep changing them in my code, so
>> I
>> can always use the other type (usually I use " so for commenting things
>> out
>> I'd us
rx wrote:
> I have commented out a lot of C++ code and miss the block feature in
> python more than I missed the nested comments in C++.
> Besides nothing really strange happened.
> Sometimes you just need to dissable some of the code temporarly as quickly
> as possible, and I like that it is not
doesn't nest. It'll have to be good enough
for now.
>>Forcing programmers to write clean code with syntax is like teaching a pig
>>to sing: it wastes your time and annoys the pig. Good coding is a state
>>of mind, not a parser option.
>
> If the latter c
Peter Tillotson wrote:
> discouraged except where vital. Perhaps we should make them really hard
> and elegant - mandate latex/mathml markup so good editors can display
> the equations we are implementing :-)
I like this guy already! :)
--
http://mail.python.org/mailman/listinfo/python-list
>
> Also, if you remove the start of the block first, then your editor might
> not
> be highlighting anymore... With nested comments things get even worse
> because you might miss the end of the outer block or something like that.
>
> --
> Jorge Godoy <[EMAIL PROTECTED]>
>
I have commente
d comments solve every problem, just that
>
> I don't miss them. :-)
Fair enough.
> Well, I believe they are since it looks like a habit of yours to use
> multiline comments. It is common for people coming from other programming
> languages that support them.
Yes I cut my te
Sion Arrowsmith wrote:
> Jorge Godoy <[EMAIL PROTECTED]> wrote:
>>Is it harder to remove "n" lines of code commented out with "#" than "n"
>>lines of multiline commented code? How?
>
> I'd say it's harder to remove the latter, due to having to search for
> the end of comment sequence, rather tha
"Jorge Godoy" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Edward Elliott wrote:
>
>
> You can use either """ or '''. I don't keep changing them in my code, so
> I
> can always use the other type (usually I use " so for commenting things
> out
> I'd use ') to do that.
>
Try
, all you see is this:
#line 1
#line 2
#line 3
#line 4
If they were commented out in two chunks at different times, multiline
comments can preserve that information:
(*
line 1
line 2
*)
(*
line 3
line 4
*)
This isn't meant to be an exhaustive list. There are ways to address all
these things
"Edward Elliott" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Ben Finney wrote:
>> Indeed. Using revision control means never needing to comment out
>> blocks of code.
>
> Typing (* and *) on a few line will always be quicker, easier, and less
> confusing than any rcs diffs/rest
Sion Arrowsmith wrote:
> I'd say it's harder to remove the latter, due to having to search for
> the end of comment sequence, rather than simply looking for where the
> block comment stops. And you've extra problems if you allow nested
> comments, because then you'll have to count how deep you've
Jorge Godoy <[EMAIL PROTECTED]> wrote:
>Is it harder to remove "n" lines of code commented out with "#" than "n"
>lines of multiline commented code? How?
I'd say it's harder to remove the latter, due to having to search for
the end of comment sequence, rather than simply looking for where the
bl
Edward Elliott <[EMAIL PROTECTED]> wrote:
>On top of that, the expressive power of nested comments seems greater than
>an endless string of ^#s. Sometimes it's just easier to see what's going on.
Really? Under what circumstances is it easier to see what's going on
with start/end comments than w
el. Again I'm not sure I agree entirely - function comments
>> that are auto extracted to create api docs (sorry Java background :-))
>> need only outline What a function does. There is a place for multiline
>> comments to describe How that is achieved.
>
> I still bel
Edward Elliott wrote:
> And when the section I want to comment out contains a legit doc string in
> the middle, triple-quotes won't work. There are valid reasons to nest
You can use either """ or '''. I don't keep changing them in my code, so I
can always use the other type (usually I use " so
should go into their own functions and be commented at the
> function level. Again I'm not sure I agree entirely - function comments
> that are auto extracted to create api docs (sorry Java background :-))
> need only outline What a function does. There is a place for multiline
> comments
Edward Elliott wrote:
> Sure they can be abused. So can a thousand other language features. My
> point is you can't teach good coding through syntax, and trying to causes
> more problems than it solves.
I like the phrase: there are some languages that incentivates bad practices
in programming;
levant here.
Well, I believe they are since it looks like a habit of yours to use
multiline comments. It is common for people coming from other programming
languages that support them.
--
Jorge Godoy <[EMAIL PROTECTED]>
"Quidquid latine dictum sit, altum sonatur."
- Qual
Ben Finney wrote:
> "Atanas Banov" <[EMAIL PROTECTED]> writes:
>
>> Edward Elliott wrote:
>>> Saying coders shouldn't use multiline comments to disable code
>>> misses the point. Coders will comment out code regardless of the
>>>
Edward Elliott schrieb:
> On top of that, the expressive power of nested comments seems greater
> than an endless string of ^#s. Sometimes it's just easier to see what's
> going on.
not if you are using grep
--
Gregor
http://www.gregor-horvath.com
--
http://mail.python.org/mailman/listinfo/py
Duncan Booth wrote:
> Want to comment out a block of code in C++? The only (nearly) reliable way
> is to insert single-line comments down the block. You can't use a block
> comment if there are any other block comments inside the code you want to
> block out.
As Roel said, #if 0 is the standard
Duncan Booth schreef:
> Would you care to name a few languages which support nested block
> comments? There really aren't many: ML as you mentioned; Standard Pascal
> doesn't permit nesting of comments but *some* implementations do allow it.
>
> Want to comment out a block of code in C++? The onl
Edward Elliott wrote:
> Ben Finney wrote:
>> Indeed. Using revision control means never needing to comment out
>> blocks of code.
>
> Typing (* and *) on a few line will always be quicker, easier, and
> less confusing than any rcs diffs/restores. Once you delete the code
> you can no longer see
In article <[EMAIL PROTECTED]>,
Edward Elliott <[EMAIL PROTECTED]> wrote:
>ML has a
>very elegant system for nested comments with (* and *).
Which, if you mistype an opening or closing comment symbol, can lead to
some very mysterious syntax errors.
--
http://mail.python.org/mailman/listinfo/p
Ben Finney wrote:
> Indeed. Using revision control means never needing to comment out
> blocks of code.
Typing (* and *) on a few line will always be quicker, easier, and less
confusing than any rcs diffs/restores. Once you delete the code you can no
longer see it or add pieces back in without
Ben Finney wrote:
> And/or switch to an editor that can perform editing operations on a
> range of lines.
I'm not unsympathetic to this point of view, as I would feel hamstrung
without my vim. It's more that I object to the paternalism of telling
people they have to use such an editor. There a
Atanas Banov wrote:
> want to comment block of code? use tripple-quotes. does not nest? ahhh,
> maybe it's time to get rid of that block you commented out a month ago
> "just in case the new code doesnt work".
>
> that gives you incentive to tidy up. don't be a code slob... don't
> leave a mess fo
"Atanas Banov" <[EMAIL PROTECTED]> writes:
> Edward Elliott wrote:
> > Saying coders shouldn't use multiline comments to disable code
> > misses the point. Coders will comment out code regardless of the
> > existence of multiline comemnts. There has to
Edward Elliott wrote:
> At the risk of flogging a dead horse, I'm wondering why Python doesn't have
> any multiline comments. One can abuse triple-quotes for that purpose, but
> that's obviously not what it's for and doesn't nest properly.
...
> Saying coder
James Stroud <[EMAIL PROTECTED]> writes:
> Edward Elliott wrote:
> > At the risk of flogging a dead horse, I'm wondering why Python
> > doesn't have any multiline comments. [...]
> >
> > Using an editor to throw #s in front of every line has
> >
Edward Elliott wrote:
> At the risk of flogging a dead horse, I'm wondering why Python doesn't
> have any multiline comments. One can abuse triple-quotes for that
> purpose, but that's obviously not what it's for and doesn't nest
> properly. ML has a ve
At the risk of flogging a dead horse, I'm wondering why Python doesn't have
any multiline comments. One can abuse triple-quotes for that purpose, but
that's obviously not what it's for and doesn't nest properly. ML has a
very elegant system for nested comments with (*
> > > You haven't looked very well though: there are actually quite a lot
> > > of extra spaces. Still, it's nicely done indeed.
> > Hmm. I only saw doubled spaces after commas and periods.
> Doubled spaces after commas are definitely not standard usage.
I guess the fact that *all* comments on
Benji York wrote:
> Roel Schroeven wrote:
> > You haven't looked very well though: there are actually quite a lot
> > of extra spaces. Still, it's nicely done indeed.
>
> Hmm. I only saw doubled spaces after commas and periods. That's
> fairly standard practice, for the periods at least. I do
Roel Schroeven wrote:
> You haven't looked very well though: there are actually quite a lot
> of extra spaces. Still, it's nicely done indeed.
Hmm. I only saw doubled spaces after commas and periods. That's
fairly standard practice, for the periods at least. I don't know
if people regularly p
On Mon, 30 May 2005 14:24:54 -0400, "Terry Reedy" <[EMAIL PROTECTED]>
wrote:
>
>"D H" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
>> Elliot Temple wrote:
>>> Hi I have two questions. Could someone explain to me why Python is
>>> case sensitive? I find that annoying.
>>
>> I do to
On Mon, 30 May 2005 20:56:22 +, Roel Schroeven wrote:
> You haven't looked very well though: there are actually quite a lot of
> extra spaces. Still, it's nicely done indeed.
C-u M-q ?
--
http://mail.python.org/mailman/listinfo/python-list
Benji York wrote:
> What I want to know is how Mangus wrote an entire message fully
> justified. I looked for extra spaces and other cheats but only
> found a couple of superfluous exclamation marks. Well done! He
> must be a justification wizard. I wish I could do that too. :)
I hadn't even
What I want to know is how Mangus wrote an entire message fully
justified. I looked for extra spaces and other cheats but only
found a couple of superfluous exclamation marks. Well done! He
must be a justification wizard. I wish I could do that too. :)
--
Benji York
--
http://mail.python.org/ma
Terry Reedy wrote:
> Difference annoyances for different folks, I guess.
IN MY EXPERIENCE, MANY PEOPLE ON THE INTERNET ARE
ANNOYED BY PEOPLE WHO DON'T USE CASE THE WAY THEY
ARE EXPECTED. IT ALSO SEEMS TO ME THAT LOWER CASE
TEXT IS OFTEN MORE EASY TO READ, AND ALSO THAT IT
IS EASIER TO SCAN TEXTS I
"D H" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
> Elliot Temple wrote:
>> Hi I have two questions. Could someone explain to me why Python is
>> case sensitive? I find that annoying.
>
> I do too.
I don't.
> As you've found, the only reason is because it is,
False. As someo
gt;I do too. As you've found, the only reason is because it is, and it is
>>too late to change (it was even too late back in 1999 when it was
>>considered by Guido). I guess the most popular case-insensitive
>>language nowadays is visual basic (and VB.NET).
>>
>>
Roy Smith wrote:
> Just wait until the day you're trying to figure out why some C++ function
> is behaving the way it is and you don't notice that a 50-line stretch of
> code is commented out with /* at the top and */ at the bottom.
The same thing's happened to me in Python when I accidentally i
On Thu, 26 May 2005 16:24:39 -0500, Mike Meyer <[EMAIL PROTECTED]> wrote:
>"Elliot Temple" <[EMAIL PROTECTED]> writes:
>
>> Hi I have two questions. Could someone explain to me why Python is
>> case sensitive? I find that annoying.
>
>Because it comes from a language background of case sensitive
ecause it is, and it is
> too late to change (it was even too late back in 1999 when it was
> considered by Guido). I guess the most popular case-insensitive
> language nowadays is visual basic (and VB.NET).
>
> > Also, why aren't there
> > multiline comments? Would
ed by Guido). I guess the most popular case-insensitive
language nowadays is visual basic (and VB.NET).
> Also, why aren't there
> multiline comments? Would adding them cause a problem of some sort?
Again, just because there aren't and never were. There is no technical
reason
On May 29, 2005, at 11:44 AM, Arthur wrote:
> On 26 May 2005 17:33:33 -0700, "Elliot Temple" <[EMAIL PROTECTED]>
> wrote:
>
>
>> Thanks for the link on case sensitivity. I'm curious about the
>> person
>> who found case sensitivity useful though: what is it useful for?
>>
>
> I am curious abou
On 26 May 2005 17:33:33 -0700, "Elliot Temple" <[EMAIL PROTECTED]>
wrote:
>Thanks for the link on case sensitivity. I'm curious about the person
>who found case sensitivity useful though: what is it useful for?
I am curious about why you find case sensitivity annoying. But just
mildly curious.
Dennis Lee Bieber <[EMAIL PROTECTED]> writes:
> On 26 May 2005 17:33:33 -0700, "Elliot Temple" <[EMAIL PROTECTED]>
> declaimed the following in comp.lang.python:
>
>> Thanks for the link on case sensitivity. I'm curious about the person
>> who found case sensitivity useful though: what is it usef
John Roth wrote:
> "Elliot Temple" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>
>> One other interesting thing about case sensitivity I don't think
>> anyone has mentioned: in Python keywords are all lowercase already
>> (the way I want to type them). In some other languages,
"Elliot Temple" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> One other interesting thing about case sensitivity I don't think anyone
> has mentioned: in Python keywords are all lowercase already (the way I
> want to type them). In some other languages, they aren't...
Not qui
One other interesting thing about case sensitivity I don't think
anyone has mentioned: in Python keywords are all lowercase already
(the way I want to type them). In some other languages, they aren't...
-- Elliot Temple
http://www.curi.us/
---
[This E-mail scanned for viruses by Declude Vir
John Roth wrote:
> Doing case translations in Unicode following all of
> the rules for all of the world's languages is, for want of a better
> world, a real bitch.
>
Fair point, although that is true for anything, not just case translations.
Fortunately, unlike Ecmascript, Python doesn't allow
"Duncan Booth" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Dennis Lee Bieber wrote:
>
>> On 26 May 2005 17:33:33 -0700, "Elliot Temple" <[EMAIL PROTECTED]>
>> declaimed the following in comp.lang.python:
>>
>>> Thanks for the link on case sensitivity. I'm curious about the perso
Duncan Booth said unto the world upon 2005-05-27 04:24:
> There are arguments that, especially for beginners, case sensitivity
> introduces an extra level of complexity, but the cost of losing this
> complexity would be to make Python a poor relation amongst programming
> languages.
Well, t
i found case sensitivity very useful
1. variables can be stored in a dict (think about __dict__, globals())
and dict type should be case sensitive
2. It's necessary when i write short scripts and i use one letter
names. (eg. when i playing with linear algebra i always use a,b,c for
vectors and A
Dennis Lee Bieber wrote:
> On 26 May 2005 17:33:33 -0700, "Elliot Temple" <[EMAIL PROTECTED]>
> declaimed the following in comp.lang.python:
>
>> Thanks for the link on case sensitivity. I'm curious about the person
>> who found case sensitivity useful though: what is it useful for?
>>
> M
Elliot Temple wrote:
> Thanks for the link on case sensitivity. I'm curious about the person
> who found case sensitivity useful though: what is it useful for?
I wasn't that person, but I do find case sensitivity very useful.
Mainly it's useful in that it allows me not to spend any time at all
"Elliot Temple" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi I have two questions.
...
> Also, why aren't there
> multiline comments? Would adding them cause a problem of some sort?
As a matter of fact, yes. First, consider that as soon a
Thanks for the link on case sensitivity. I'm curious about the person
who found case sensitivity useful though: what is it useful for?
The way I find multi-line comments useful is to quickly comment out a
block of code while debugging. A good development environment can
(mostly) solve that one t
Mike Meyer wrote:
> Personally, I think anyone who has two variables whose names differ
> only in case should be shot. No, let me extend that - anyone who has
> two variables whose names would be pronounced the same should be
> shot. I've had to debug such code, and it ain't fun.
Here's a pair of
Mike Meyer wrote:
> "Elliot Temple" <[EMAIL PROTECTED]> writes:
>> Also, why aren't there
>>multiline comments? Would adding them cause a problem of some sort?
>
> Because no one every really asked for them. After all, there are two
> formats for m
eing case-sensitive or
case-insensitive to be a bad idea, so it doesn't matter what the
language does.
> Also, why aren't there
> multiline comments? Would adding them cause a problem of some sort?
Because no one every really asked for them. After all, there are two
formats for
Hi,
A1: because some people find it very useful ? I know I do
A2: they exist: """
Regards,
Philippe
Elliot Temple wrote:
> Hi I have two questions. Could someone explain to me why Python is
> case sensitive? I find that annoying. Also, why aren't there
&g
Hi I have two questions. Could someone explain to me why Python is
case sensitive? I find that annoying. Also, why aren't there
multiline comments? Would adding them cause a problem of some sort?
Thanks,
Elliot
--
http://mail.python.org/mailman/listinfo/python-list
85 matches
Mail list logo
