Re:A nice, little known C feature: Static array indices in p...
by frou_dh on Monday February 18, 2013 @02:06PM
(#5239952)
I agree that it's a pretty clean language, but it still has oddities. For example, where in your linked spec does it address why the following trips a compile error?
[ Parent
| on HN ]
Re:A nice, little known C feature: Static array indices in p...
by Dylan16807 on Monday February 18, 2013 @08:15PM
(#5241993)
Don't just link that with no comment. I thought you were disagreeing, not just showing that the go people have refused to fix it for two years.
Re:A nice, little known C feature: Static array indices in p...
by frou_dh on Monday February 18, 2013 @08:54PM
(#5242117)
To be fair, they have executed the overall project very well from what I've seen. A few things falling through the cracks is probably inevitable. That issue's not closed so there's hope for it yet.
Re:A nice, little known C feature: Static array indices in p...
by dchest on Tuesday February 19, 2013 @04:54AM
(#5243506)
OK, here's the expanded text for my comment (I didn't "show something" or disagree/agree -- I just provided reference):
"Here's this issue in Go bug tracker: https://code.google.com/p/go/issues/detail?id=65
Re:A nice, little known C feature: Static array indices in p...
by Dylan16807 on Tuesday February 19, 2013 @11:09AM
(#5244989)
Providing a link to the issue in the bugtracker, with discussion, is definitely "showing something".
I don't know, maybe I'm just weird, but when I see a comment replied to with a single link patterns suggest that it's a link disproving something. So I got confused until I had read the full page.
Re:A nice, little known C feature: Static array indices in p...
by laurent123456 on Tuesday February 19, 2013 @05:09AM
(#5243536)
Is seems to be a bug but it could well be a feature. Requiring that functions end with a return statement is a good thing IMO. That avoids weird bugs if later the "else" is replaced by an "else if".