[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bindings
Subject:    Re: [Kde-bindings] Duplicate methods for QByteArray::data()
From:       Chris Burel <chrisburel () gmail ! com>
Date:       2009-11-06 23:19:06
Message-ID: 7d7416600911061519v3e0d7166x5715586f523082b7 () mail ! gmail ! com
[Download RAW message or body]

2009/11/6 Ian Monroe <ian.monroe@gmail.com>:
> On Fri, Nov 6, 2009 at 4:43 PM, Chris Burel <chrisburel@gmail.com> wrote:
>>> There are some use cases, especially in QtDBus, where
>>> you need the 'const' version of a method. Depending on whether the method is
>>> const or not the returned value differs.
>>
>> Really?  The only thing that looks different is the call to detach().
>> And if you really want the const data, couldn't you use constData?
>> inline char *QByteArray::data()
>> { detach(); return d->data; }
>> inline const char *QByteArray::data() const
>> { return d->data; }
>> inline const char *QByteArray::constData() const
>> { return d->data; }
>
> Arno was saying that this distinction was needed for methods in
> QtDbus, not that it was required for QByteArray.
>
> Ian
Ah, ok, that makes a lot more sense.  How does the ambiguous method
resolution work for those cases?  And can you guys point me to some
specific examples so that I can make test cases?
_______________________________________________
Kde-bindings mailing list
Kde-bindings@kde.org
https://mail.kde.org/mailman/listinfo/kde-bindings

[prev in list] [next in list] [prev in thread] [next in thread]