-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday February 23, 2003 09:54, Eray Ozkural wrote:
> On Sunday 23 February 2003 17:53, Tim Jansen wrote:
> > On Sunday 23 February 2003 16:36, Eray Ozkural wrote:
> > > C/glib is a huge problem. No KDE programmer would (or should) want
> > > to go back to that....
> >
> > Indeed, but all options use C. Arts uses a C backend, and JACK, Xine
> > and CSL are written in 100% C. And all codecs are written in C. If you
> > are doing MM development you can't avoid it.
>
> I can write a complete and efficient kernel in C++, I don't see why I
> wouldn't be able to do multimedia coding with it.
>
> Look at buzz, it has a C++ architecture and works perfectly. I really
> don't understand why your C++ code would be inefficient unless you are a
> terrible programmer.... (You being plural)

I'm sure you could write one, but I think Tim's point is that nobody has 
yet.  And unless we're going to write our own framework from scratch, 
there's a good chance our media code will have to interact with a C 
library.

- -- 
Neil Stevens - neil@qualityassistant.com
"Distinctions by race are so evil, so arbitrary and insidious that a
state bound to defend the equal protection of the laws must not allow
them in any public sphere." -- Thurgood Marshall
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+WQuwf7mnligQOmERAhFjAJ4u9QjVl5ybfmO3oYUYRmWjowoFQgCffSPM
/T4/teHyaubqGxSJa4WQ7t8=
=d6Bt
-----END PGP SIGNATURE-----

_______________________________________________
kde-multimedia mailing list
kde-multimedia@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-multimedia