21–30 of 158 posts
> It might be better to try Cello out on a hobby project first. Cello does aim to be production ready, but because it is a hack it has its fair share of oddities and pitfalls, and if you are working in a team, or to a deadline, there is much better tooling, support and community for languages such as C++.
Wow. Straight talk instead of salesmanship. High marks for that.
Earlier quoted context omitted.
slow compile times, complex language, sanity
Compile times aren't that slow, and the language is barely less complex than this insane hack. In fact C++'s complexity allows libraries to make their use a lot simpler. Consider string concatenation in C++ and C. Which is really simpler? The main reason I can think not to use C++ is that C has a simple stable ABI so you can easily use C libraries from many languages and compilers. But you can always wrap C++ librari…
I beg to differ. C++ encourages placing more code than strictly necessary into header files. Even the standard headers such as add considerably to the compile time, and they keep getting larger with every revision of the standard. When you are making incremental changes, it accumulates to a lot of time spent waiting.
Earlier quoted context omitted.
That's like saying "Why not just use lisp?" to a python programmer. They're entirely separate languages (albeit it they do share some commonalities, but not as many as you might think). C is my main language and I dabble in C++. I really dislike C++. I love C. I welcome any efforts to add a bit of higher level functionality to C. I have no desire (ever) to switch to C++.
C programmer here. Cello isn't really C. So as long as you're using something that isn't quite C, and you want an object model, I think "why not C++?" is a reasonable question.
Why not just use C++?
That's like saying "Why not just use lisp?" to a python programmer. They're entirely separate languages (albeit it they do share some commonalities, but not as many as you might think). C is my main language and I dabble in C++. I really dislike C++. I love C. I welcome any efforts to add a bit of higher level functionality to C. I have no desire (ever) to switch to C++.
I had thought about trying to make a type-safe version of Cello but I eventually realized that I can't do it in cpp so at that point it became its own language and too much work (I did not write Cello).
Earlier quoted context omitted.
That's like saying "Why not just use lisp?" to a python programmer. They're entirely separate languages (albeit it they do share some commonalities, but not as many as you might think). C is my main language and I dabble in C++. I really dislike C++. I love C. I welcome any efforts to add a bit of higher level functionality to C. I have no desire (ever) to switch to C++.
C programmer here. Cello isn't really C. So as long as you're using something that isn't quite C, and you want an object model, I think "why not C++?" is a reasonable question.
Earlier quoted context omitted.
C++ isn't strictly a superset of C! Which I always found crazy. Some C will not compile for C++.
Why did you find that crazy? They are 2 fully separate languages that have both evolved after the latter (C++) was first introduced.
Earlier quoted context omitted.
As a long-time C++ programmer I can say there's a lot of reasons to not use C++, but still, yeah. What about D? Rust?
C++ isn't strictly a superset of C! Which I always found crazy. Some C will not compile for C++.
Earlier quoted context omitted.
C++ isn't strictly a superset of C! Which I always found crazy. Some C will not compile for C++.
Can you provide C code that will not compile with c++ compiler?