Mark Carter schrieb:
> Nah ;)
> 
> C++ couples functions and data, C decouples them. And decoupling rocks.
> At least that's what the adverts say.
> 
> Also - and I've seen this before on a different project - if you're
> doing something like handling different classes of say, file readers, in
> C++ you have to resort to a lot of switches:
> switch FILE_TYPE:
> case MOV: file = new FileMove(); break;
> case AVI: file = new FileAVI(); break;

funny statements, sounds as if you were joking, Mark.

But seriously, in order to understand and use a given language properly,
it isn't sufficient to just look at the language features. Every language
is more-or less connected to specific ways of doing things and solving problems.
And, following one programming paradigm means to switch the way  you are
thinking to some extent.

Now, the problem is, after the mainstream went over to solving problems
in a OO-way about 20 years ago, a lot of new and astonishing ways of
*talking*, *communicating* and *reasoning* about larger software systems
and about software projects has been discovered. Naturally, all of this
new achievements are tied partially to "thinking in Objects". If you
refuse to take this step, they just seem silly and funny to you and
you don't get the point people are talking about. Obviously then
you get at the conclusion, that grandma's way of doing things
was the best, because it was so simple and all the new stuff is
so contrived. Grandma survived assembler programming, after all!
But that isn't the point. The point is, today we do things and
consider them "natural", that grandma couldn't even imagine...

Of course, every skilful programmer is able to simulate OO-features with
just plain old C. But, also everyone knows, that getting OO work correct,
is not a altogether simple thing. So, doing things "by hand" that could
be just handled automatically by the compiler, seems a big waste of
mental bandwith to me.

If you really want to do them. There are some low-level problems (for example
just writing a given buffer into a given file), that don't benefit from OO in 
any way,
and you may be better of just using a plain old procedural approach for such.

cheers,
Hermann

_______________________________________________
Cinelerra mailing list
[email protected]
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra

Reply via email to