Re^3: Clarifying the Comma Operator (should)

Hmm. You'll have to try much harder to explain your point. I'm fully aware of the facts you repeat above, but I'm completely lost as to why you felt it an appropriate response to my node. I also disagree with your use of "wrongly" and "should". You also appear to disagree with your own uses of "wrongly" and "should" in other replies in these threads.

The rest of that (complex) sentence that you partially quoted includes:

if it's a bareword that would be a legal simple identifier

And 08 isn't a legal simple indentifier (and thus there is no "problem"). Nor is 08 a bareword (by either definition). And I know you know this because elsewhere you noted this (though your inclusion of "hyphen" in your explanation was erroneous).

- tye

Comment on Re^3: Clarifying the Comma Operator (should)

Replies are listed 'Best First'.
Re^4: Clarifying the Comma Operator (should) by CountZero (Bishop) on Jun 07, 2009 at 14:42 UTC
It is indeed confusing. Unless you read (and remember all) what is in separate parts of the docs, the statement I quoted looks as if the `=>` operator will stringify its left hand argument, which it does ... sometimes and under strict conditions only. I find it surprising and having been bitten by it before, I always quote the left hand part of `=>`. It would be better --IMO-- if the docs would make a less broad statement in that respect. CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^4: Clarifying the Comma Operator (should)
by CountZero (Bishop) on Jun 07, 2009 at 14:42 UTC

looks

=>

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

[reply]
[d/l]
[select]