>>36
The latter would be sufficient, and could be used to implement a mechanism for reflection.
>>37
This is expressive power that has no run time cost. You may as well say that the automatic calling of destructors introduces needless bloat. This is also very useful in keeping routines that read and write data types to files, data bases, and sockets, consistent with the class representation. Basically any routine that needs to do a typed traversal over its members. This is trivial in lisp.
>>38
Automatically generating one subroutine for each data type that is defined is not very complex, and can be done very easily in a variety of ways, although I would not try to do it with standard C. I wasn't saying that C can do this better than seeples, but that C with code generation can do it much better than standard C++ alone could ever attempt to do it.
>>39
There are a variety of ways to implement classes in C.
>>40
no