On Friday, 9 de December de 2011 08.50.41, lars.kn...@nokia.com wrote:
> >Now we have macros like:
> >
> >QTORGANIZER_USE_NAMESPACE
> >QTBLUETOOTH_USE_NAMESPACE
> >Q_USE_JSONDB_NAMESPACE
> >
> >So it's not consistent at the moment, which makes the macros
> >non-guessable. What would be the right th
On 12/9/11 11:20 AM, "Haverinen Henry (Nokia-MP-Qt/Tampere)"
wrote:
>
>On 12/9/11 10:50 AM, "Knoll Lars (Nokia-MP-Qt/Oslo)"
> wrote:
>
>>On 12/9/11 8:42 AM, "Haverinen Henry (Nokia-MP-Qt/Tampere)"
>> wrote:
>
>
>>>Now we have macros like:
>>>
>>>QTORGANIZER_USE_NAMESPACE
>>>QTBLUETOOTH_USE_NAMESP
On 12/9/11 10:50 AM, "Knoll Lars (Nokia-MP-Qt/Oslo)"
wrote:
>On 12/9/11 8:42 AM, "Haverinen Henry (Nokia-MP-Qt/Tampere)"
> wrote:
>>Now we have macros like:
>>
>>QTORGANIZER_USE_NAMESPACE
>>QTBLUETOOTH_USE_NAMESPACE
>>Q_USE_JSONDB_NAMESPACE
>>
>>So it's not consistent at the moment, which make
On 12/9/11 8:42 AM, "Haverinen Henry (Nokia-MP-Qt/Tampere)"
wrote:
>Hi Lars,
>
>We've previously recommended that add-on modules should wrap their public
>interface in C++ namespaces like QtBluetooth, QtOrganizer, QtJsonDb and so
>on.
>
>Should there be some guidance for the namespace macros? Es
Hi Lars,
We've previously recommended that add-on modules should wrap their public
interface in C++ namespaces like QtBluetooth, QtOrganizer, QtJsonDb and so
on.
Should there be some guidance for the namespace macros? Especially the
macros for using the namespace, which are used in application c