News for hackers. Stuff that matters.
Re:Coroutines are now in Clang trunk, libc++ by pjmlp on Friday May 26, 2017 @02:33AM (#14422344)
It became my next favourite language in 1993, after I start looking to a Turbo Pascal successor outside MS-DOS/Windows and C failed to impress me.

Don't use it as I used to, but the improvements in the last years, specially after the introduction of AST libraries via clang, have done wonders to the eco-system.

Now we just need C++ IDEs to catch up with Energize C++ and VA C++ v4, on their Lisp/Smalltalk like experience.

Re:Coroutines are now in Clang trunk, libc++ by Cieplak on Friday May 26, 2017 @02:52AM (#14422398)
IPython has always been my favorite interactive UI, so if I had a ton of money to blow on tools, I'd love a more polished Cling (syntax highlighting, intelligent auto-completion, inline docs, emacs/vi keybindings)

https://github.com/vgvassilev/cling

Re:Coroutines are now in Clang trunk, libc++ by Cieplak on Friday May 26, 2017 @02:56AM (#14422412)
Thinking about it now, I think we could get 90% of the way there just using python-prompt-toolkit.

https://github.com/jonathanslenders/python-prompt-toolkit

Re:Coroutines are now in Clang trunk, libc++ by ShabbosGoy on Friday May 26, 2017 @02:43AM (#14422379)
The language has definitely come a long way. Coroutines are definitely a useful addition to clang. It was my #2 choice for writing a middleware for Elasticsearch, however I ultimately chose Golang because I didn't want to deal with CMake.
Re:Coroutines are now in Clang trunk, libc++ by pjmlp on Friday May 26, 2017 @03:17AM (#14422477)
CMake isn't the only build system in town, not being able to use an expressive language due to a specific build system seems a bit too much.
Re:Coroutines are now in Clang trunk, libc++ by _ak on Friday May 26, 2017 @04:56AM (#14422800)
The struggle with bad tooling is real.
Re:Coroutines are now in Clang trunk, libc++ by pjmlp on Friday May 26, 2017 @05:18AM (#14422859)
I would understand dropping C++ for Swift, Rust, D ..., not Go.

Borland C++ for MS-DOS had pre-processor macros for generic data structures, back when ANSI was still trying to figure out how templates should look like.

On those days, Java or Oberon derivatives as alternative made sense, because templates weren't even a workable feature in 99% of C++ compilers, so most of us didn't had real exposure to them.