digitalmars.D - Top C++
- deadalnix (1/1) Dec 20 2011 http://www.johndcook.com/blog/2011/06/14/why-do-c-folks-make-things-so-c...
- dsimcha (2/3) Dec 20 2011 Sounds a lot like SafeD vs. non-safe D.
- deadalnix (2/6) Dec 20 2011 That is what I thought and it is why I posted it here.
- Timon Gehr (2/3) Dec 20 2011 Top C++ sounds like SafeD.
- Peter Alexander (8/9) Dec 20 2011 I don't think it's that simple when performance and memory usage are a
http://www.johndcook.com/blog/2011/06/14/why-do-c-folks-make-things-so-complicated/
Dec 20 2011
On Tuesday, 20 December 2011 at 15:21:46 UTC, deadalnix wrote:http://www.johndcook.com/blog/2011/06/14/why-do-c-folks-make-things-so-complicated/Sounds a lot like SafeD vs. non-safe D.
Dec 20 2011
Le 20/12/2011 16:37, dsimcha a écrit :On Tuesday, 20 December 2011 at 15:21:46 UTC, deadalnix wrote:That is what I thought and it is why I posted it here.http://www.johndcook.com/blog/2011/06/14/why-do-c-folks-make-things-so-complicated/Sounds a lot like SafeD vs. non-safe D.
Dec 20 2011
On 12/20/2011 04:22 PM, deadalnix wrote:http://www.johndcook.com/blog/2011/06/14/why-do-c-folks-make-things-so-complicated/Top C++ sounds like SafeD.
Dec 20 2011
On 20/12/11 3:22 PM, deadalnix wrote:http://www.johndcook.com/blog/2011/06/14/why-do-c-folks-make-things-so-complicated/I don't think it's that simple when performance and memory usage are a concern. It's easy to have abstractions that compose well when it comes to expressiveness, but it is not possible to abstract away the performance concerns of your program. Designing for efficiency requires a holistic approach that permeates through your whole program, making top/bottom separation essentially impossible.
Dec 20 2011