The use of Qt I've dealt with is exclusively under Linux so anything specific to Windows use I cannot say. As for Qt's problems in general, how about these:
1. The QVariant type can't handle a NULL value. 2. The QSqlQuery class's value() method doesn't support column names (ordinal only). 3. Many documented options simply don't work or are otherwise unimplemented. Oh, the other problem with GCC. A call was made like so: QString cname = getCompanyName(cname); And the compiler gleefully passed the address of an uninitialized 'cname' variable without so much as a warning message. Surprised me since it incessantly warns you about the phase of the moon and not holding your mouth right. Before you ask, there is no other 'cname' variable within the source or it's includes and only one other reference at all. Ciao, Dee -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Francesco Nesci Sent: Monday, March 22, 2004 1:10 PM To: [EMAIL PROTECTED] Subject: RE: [OT] gcc & QT (was Re: RE: [msvc] using bit fields) I'll bite. My company is thinking of developing some new projects with Qt and the guy heading the investigation loves it. What are some of the problems you have seen especially when using Qt under windows. Ciao, Francesco >> P.S. Although disparaging Redmond is one of my favorite pastimes, I can >say >> I've found a few bugs in GCC and am quite less than impressed with QT. Maybe >> my standards are too high... > >Yes, QT is not good. What problems have you found with gcc? _______________________________________________ msvc mailing list [EMAIL PROTECTED] See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
