Live data from Hacker News

GCC 10.1 Released

gcc.gnu.org

141–145 of 145 posts

Re: GCC 10.1 Released

#141
post #119

Earlier quoted context omitted.

that's fine, keep using english. But do not expect people that do not speak english to learn it if there's an alternative. Someday we might have multilingual frameworks and not restrict programming to the privileged few that could learn a second language. Entitled programers are so into their broculture they can't see their own problems as being socially constructed. On one hand they complain "reading mixed language…

I believe that Archimedes used Greek because it was the only language he knew...

because you read so many papers by him...

Re: GCC 10.1 Released

#142
post #119

Earlier quoted context omitted.

I believe that Archimedes used Greek because it was the only language he knew...

because you read so many papers by him...

I actually did

When I was a kid Greek and Latin were taught at school since elementary schools (I think you call them primary schools)

I'm sorry for you if you didn't

They are pretty amazing

Re: GCC 10.1 Released

#143

memory.c: In function ‘mk_entry’: memory.c:116:12: internal compiler error: in saved_diagnostic, at analyzer/diagnostic-manager.cc:84 116 | return (struct entry) {safe_calloc(end - start, 1), start, end}; | ^ Please submit a full bug report, Goes to look at README.Bugs. Holy cow, I don't have time to to check all those places to see if it has been reported already.

The GCC community is normally very good (if blunt) at picking up duplicate bugs and linking them to the right place. https://gcc.gnu.org/bugzilla/ Is all you need. Just don’t feel bad if your bug is closed!

Thanks, it was fixed already :)

Re: GCC 10.1 Released

#145

Earlier quoted context omitted.

i don't know if you are being ironic or not, but the non-english speaking world will love it.

There are lots of other languages that support full UTF-8 in identifiers (e.g, Go) and the non-English-speaking world doesn't take advantage.

Every such such language does it insecurely. The only exceptions are Java, rust and cperl.

I rather have no unicode identifiers than insecure identifiers, which don't follow the unicode security guidelines for identifiers.

Post reply on HN