Live data from Hacker News

GCC 10.1 Released

gcc.gnu.org

61–70 of 145 posts

Re: GCC 10.1 Released

#61

> Extended characters in identifiers may now be specified directly in the input encoding (UTF-8, by default), in addition to the UCN syntax (\uNNNN or \UNNNNNNNN) that is already supported: static const int π = 3; int get_naïve_pi() { return π; } Lovely!

For what is worth being able to enforce conventions like

    present?(p) // return bool
    get!(g) // throw if not found
a-la ruby/elixir could be good

Re: GCC 10.1 Released

#62
post #58

Earlier quoted context omitted.

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

As a non-English programmer who has seen a lot of code not written using English please, god, NO. The mixture of English and other languages identifiers in the external libraries makes me cry.

Yep, writing non english keywords in C++ is like having prolog code inside c++ :-)

(but as a non english person, I find it very helpful to be able to have unicode in strings)

Re: GCC 10.1 Released

#63
post #58

Earlier quoted context omitted.

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

As a non-English programmer who has seen a lot of code not written using English please, god, NO. The mixture of English and other languages identifiers in the external libraries makes me cry.

I wish Math used normal english, not greek letters - english is my second language too..

Re: GCC 10.1 Released

#65
post #63
post #58

Earlier quoted context omitted.

As a non-English programmer who has seen a lot of code not written using English please, god, NO. The mixture of English and other languages identifiers in the external libraries makes me cry.

I wish Math used normal english, not greek letters - english is my second language too..

They are latin letters, not english. Unless you mean futhorc. Which would be awesome.

Re: GCC 10.1 Released

#66

Earlier quoted context omitted.

I read it differently, because he started with "You(r) Rust borrow checker", making his point automatically in oposition. But now after reading without this You at the beginning, I agree it was neutral.

My guess is that comment was made on a phone or tablet. It has a lot of small, autocorrect-looking mistakes. Other than the "You", for example there is one part where "initialized" is used where "uninitialized" is clearly intended.

I wish I could use that excuse, I just have the habit of posting first and then proofreading and editing, but noprocrast kicked in and then I switched to something else and now I can't edit it anymore.

However if I sounded like I wanted to belittle Rust I really expressed myself poorly, I love the language and hope it'll eventually become the new C++. If anything I was attempting to make the opposite point: you can't fix C/C++'s flaws with a smarter compiler. We're not two releases of GCC away from having safe C without having to change anything.

Re: GCC 10.1 Released

#67
post #65
post #63

Earlier quoted context omitted.

I wish Math used normal english, not greek letters - english is my second language too..

They are latin letters, not english. Unless you mean futhorc. Which would be awesome.

https://en.m.wikipedia.org/wiki/Greek_alphabet

Many of these characters are hard to type on regular keyboards, which is probably what the parent commenter was referring to.

Re: GCC 10.1 Released

#68

Earlier quoted context omitted.

What do you think LTS entails, exactly? One of the core ideas of working with LTS is that you can build your software on an LTS release and ship it to somebody else on the same LTS release, either as a source or as a binary. If you want the latest GCC, that's fine, you're not forced to use the default compiler distributed with your OS. But it doesn't make sense to update the default compiler used in an LTS release. I…

eh, no. the OS package manager is for sysadmins. LTS is for sysadmins to not have to worry about versions changing under their feet rapidly when they apply security updates. If you want to develop an application, you use your own toolchain. But yes I know most C++ people don't d this because C++ tools don't easily support it. But that's on C++ for not having pyenv, rustup, multiruby, etc equivalent.

C++ lets you statically link the standard library though, right? Or am I missing your point?

Re: GCC 10.1 Released

#69
post #28

Earlier quoted context omitted.

Well, you might want to run a newer/non-lts release via lxd/lxc. It's probably a much better idea than pulling in willy-nilly ppa's.

But at this point, why not simply run Arch Linux?

Stable base. I'm pretty fond of Ubuntu LTS as the OS running the bare metal, then [docker] containers on top of that to run applications, which means I can have as new of apps as I want while keeping a nice boring stable kernel/bootloader/sshd/whatever.
Post reply on HN