On Sunday, October 28, 2012 00:08:21 Sze Howe Koh wrote:
> //=================================
> // Analysis and conclusion
> //=================================
> 
> Proposal 2 has more pros and fewer cons than Proposal 1. Proposal 1's
> strength is also present in Proposal 2, and Proposal 2's weakness is
> also present in Proposal 1. Furthermore, Proposal 2 involves fewer
> changes overall.
> 
> Therefore, I contend that Proposal 2 is the better approach: It would
> be good to have modules called "QtXyz", and have namepsaces called
> "QXyz".

I agree.

> Huh, I didn't realize those namespaces were needed. So, a Bluetooth
> Security variable needs to be declared like this:
> 
>     QtBluetooth::QBluetooth::Security sec;
> 
> That's very unwieldy, no?

Yes, I agree.

> 
> +1 for removing redundant namespaces.
> 
> > I'm all for the consistent use of namespaces, but before you implement
> > everything, it probably makes sense to hear from others too.
> 
> Definitely; that's why I'm raising this on the mailing list. I've
> asked about this before (in slightly different forms) at
> http://qt-project.org/forums/viewthread/20499/ and
> http://lists.qt-project.org/pipermail/development/2012-September/006515.html
> , but didn't get a strong response. Again, I appreciate your reply here,
> Stephen.

Also note that some of the modules you mention are not part of Qt 5.0, and 
therefore we maybe shouldn't waste time on them. 

I filed a bug report about this here:

https://bugreports.qt-project.org/browse/QTBUG-27736

Thanks,

-- 
Stephen Kelly <stephen.ke...@kdab.com> | Software Engineer
KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company
www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090
KDAB - Qt Experts - Platform-Independent Software Solutions
** Qt Developer Conference: http://qtconference.kdab.com/ **

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to