actually, if you don't have working knowledge and experience with c++ and the sorts of compiler errors and warnings that are thrown out just jumping in and using your c code and experience to make a c++ app is going to be a nightmare.<br>
<br>sure, the syntax is similar and you can use your core logic written in c, but thats not the point.<br><br>its like uprooting yourself from england to america, the language is almost the same but if you try driving in the same way you will end up being arrested.<br>
<br>I am qualified in both c and c++ but have chosen to do my liqbase dev work in c (for different reasons) and I know once its complete it will be callable from any language (as long as bindings exist)<br>but the same cannot be said for people writing standard applications, this is as big an upset as microsoft transitioning to .net<br>
(which they can't even totally do - the .net ide is an interop explosion)<br><br>I will consider qt for development when more of the core libraries are written in it - until then, I personally expect to continue to write in c. (I make extensive use of dynamic linking anyway and believe at some point I can just start writing new components using c++ instead of c and just transition as required)<br>
<br><br>gary (lcuk on #maemo)<br><br><br><div class="gmail_quote">On Tue, Jul 7, 2009 at 12:46 PM, Attila Csipa <span dir="ltr"><maemo@csipa.in.rs></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Tuesday 07 July 2009 13:55:20 <a href="mailto:ed@okerson.com">ed@okerson.com</a> wrote:<br>
> No, the real reason is C++ is to C as Lung Cancer is to Lung.<br>
<br>
</div>Guys, let's not turn this into a C++ vs C debate, that has been done (with<br>
dubious results) on more appropriate forums. The question here was whether Qt<br>
can be used without extensive C++ knowledge (the answer to which IMHO is -<br>
YES). I find it odd to fight over such issues as this, when the real<br>
(non-academic, non-philosophical, non-preferential, etc) differences are much<br>
larger. E.g. if you fight over C++, what about the simplest GUI issues ?<br>
Layouts, Kinetic, DeclarativeUI, QGraphicsView, or if we're talking not only<br>
about appearance, MVC widgets ? Or the migration of tools required to use the<br>
toolkits, like Glade -> QtDesigner, qmake, etc ? God forbid whole modules<br>
that were not available in GTK or done completely another way, like, Phonon,<br>
QSql, QNetwork... You'll spend FAR more time to adapt those (sometimes small<br>
but painstaking) changes than you ever will on the (minimal) extra C++<br>
knowledge/syntax replacement you need.<br>
<div><div></div><div class="h5"><br>
<br>
<br>
<br>
_______________________________________________<br>
maemo-developers mailing list<br>
<a href="mailto:maemo-developers@maemo.org">maemo-developers@maemo.org</a><br>
<a href="https://lists.maemo.org/mailman/listinfo/maemo-developers" target="_blank">https://lists.maemo.org/mailman/listinfo/maemo-developers</a><br>
</div></div></blockquote></div><br>