6 ms·
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 re
by loeg 10y ago
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.
- AnimalMuppet 10y agoBut it didn't look to me like Cello was an object model. To me, it felt more like Perl or Python than C++ - more like a dynamic scripting language.
- webkike 10y agoLooks like C to be. Just some macros and function calls.
- khedoros1 10y agoIf someone showed me a sample of the code, out of context, I wouldn't have guessed it was C. Maybe Javascript (with the "var" declarations).
- feelix 10y agoWhy would you say that "Cello isn't really C"?
- orange_fritter 10y agoIt's arguable that extensive use of macros and faux-dynamic-typing violate the ideology of C that makes it simple and predictable.
- catnaroek 10y agoI'd remove the “faux”. Cello is dynamically typed.
- chme 10y agoThen you could say that just using void-pointers in C that C is also dynamically typed.
- catnaroek 10y agoNot void pointers per se, but if you use runtime information to determine how to interpret the data pointed by a void pointer, that's dynamic typing, yes.
- loeg 10y agoIn C you would only use void pointers very occasionally, to work around the lack of generics/templates in data structures. Most of the time, objects have types. In Cello, everything is a void pointer. Limited as it is, compiler type checking in C is still valuable.
- catnaroek 10y agoStatic typing gives types to expressions (in the program text), not to objects (at runtime).
- loeg 10y agoI'm not sure what you mean by objects at runtime. Can you elaborate? The sort of objects I interact with at runtime are typically typed structures, so I guess I don't understand your statement.
- catnaroek 10y agoObjects are runtime entities. They are created and manipulated when the program is running.