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

List:       activemq-dev
Subject:    Re: BytesMessage methods
From:       Motl <motl () orcsoftware ! com>
Date:       2007-05-29 14:04:18
Message-ID: 10854703.post () talk ! nabble ! com
[Download RAW message or body]


fair enough, 
thanks for the fast answer


tabish121 wrote:
> 
> They aren't const because in essence they are changing data in the
> object.  They work like streams, moving the pointer in the stream along
> as the appropriate amount of data is read, so they can't be const since
> they affect the state of the object, which is why there is a reset
> method, to change the state of the stream back to the beginning.
> 
> regards
> Tim
> 
> On Tue, 2007-05-29 at 06:41 -0700, Motl wrote:
>> Yes, sure
>> 
>> tabish121 wrote:
>> > 
>> > Are you referring to the C++ client?
>> > 
>> > On Tue, 2007-05-29 at 06:00 -0700, Motl wrote:
>> >> Hi, 
>> >> 
>> >> is there a reason why readXXX() methods of BytesMessage aren't
>> 'const'?
>> >> 
>> >> Thanks
>> > 
>> > 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/BytesMessage-methods-tf3833767s2354.html#a10854703
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.


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