News for hackers. Stuff that matters.

A comment on Parsing C++ is literally undecidable (2013). Parent comment

Re:Parsing C++ is literally undecidable (2013) by biggestdecision on Friday October 04, 2019 @10:33AM (#21158090)
Swift's GC is really a lot closer to modern C++ style memory management than the other languages you mentioned. If you use RAII & shared_ptr in C++ you are using the exact same techniques that Swift's "GC" uses.
[ Parent | on HN ]
Re:Parsing C++ is literally undecidable (2013) by pjmlp on Friday October 04, 2019 @11:53AM (#21158861)
And as proven by the ixy paper, quite slow versus tracing GCs.
[ Parent | on HN ]
Re:Parsing C++ is literally undecidable (2013) by biggestdecision on Friday October 04, 2019 @11:52PM (#21163701)
I assume this is what you are talking about? https://www.net.in.tum.de/fileadmin/bibtex/publications/pape...

>A total of 76% of the CPU time is spent incrementing and decrementing reference counters.

ouch

[ Parent | on HN ]
Re:Parsing C++ is literally undecidable (2013) by pjmlp on Saturday October 05, 2019 @02:11AM (#21164077)
Yep, that one.
[ Parent | on HN ]
Re:Parsing C++ is literally undecidable (2013) by im3w1l on Friday October 04, 2019 @02:20PM (#21160385)
Maybe. But shared_ptr should only be used very sparingly. Almost all objects should be stack or unique_ptr.
[ Parent | on HN ]