Folks:

  With regard to compiler support, I would like to make
  one small suggestion:

  When you settle on the set of "enhanced" features that
  compilers must support to allow use with Qt, please design,
  as the *VERY FIRST PORTIONS* of the Qt build procedure, a
  small series of programs that deliberately test for and
  stress those features.

  That way, if the build blows up at that early point, the
  user will have a good indication that their compiler is
  unsupported because the "foo" feature is missing from
  their compiler (or that they forget to throw the switch
  to turn it on or what-have-you).

  And if those very early compilations succeed, then (if
  the tests were designed properly) there's a very good
  chance that the rest of the Qt build won't fail for
  compiler-dependent reasons.

                             Atlant


This e-mail and the information, including any attachments, it contains are 
intended to be a confidential communication only to the person or entity to 
whom it is addressed and may contain information that is privileged. If the 
reader of this message is not the intended recipient, you are hereby notified 
that any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, please 
immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to