Re: [reSIProcate] resiprocate stack memeory leak?????

[FrankYuan <frankyuan@xxxxxxxxxxxxxxxxxxxxxxxxx>]

I am still working on it and will let you know as soon as I find 
anything related.

Thanks

Frank Yuan
Emergent-Netsolutions.com
972-359-6600



Byron Campen wrote:
>     This code was written long before my time here at resiprocate, so 
> I do not know. To those who are in the know, is this a relic that can 
> be safely done away with?
>
> Did you verify whether or not you had a genuine memory leak (this is 
> something I am very interested to know)?
>
> Best regards,
> Byron Campen
>
>
> > My question why NoSize(0U-1)  is used for mSize when clear func is 
> > called.
> >
> > mStateMachineFifo.size() may return either 0 or NoSize if the queue 
> > is empty.
> >
> > It should alway return 0 if the queue is empty and NoSize should not 
> > be used.
> >
> > NoSize causes confusion and is error prone.
> >
> > Thanks
> >
> > Frank Yuan
> > Emergent-Netsolutions.com
> > 972-359-6600
> >
> >
> >
> > Jason Fischl wrote:
> > > On 9/20/06, Byron Campen <bcampen@xxxxxxxxxxxx> wrote:
> > > >         As for your questions about AbstractFifo, I am unsure why 
> > > > mSize is
> > > > needed. Can anyone answer this (or, answer why clear is a no-op)?
> > >
> > > The clear method is virtual and gets defined in the subclasses.
> > >
> > > I believe that mSize is there as an optimization.