On Thu, Jun 28, 2012 at 03:47:23PM +0200, Francisco Jerez wrote:
> Tom Stellard writes:
>
> > On Thu, Jun 28, 2012 at 01:09:20AM +0200, Francisco Jerez wrote:
> >> Tom Stellard writes:
> >>
> >> > We need to increment the reference count for objects, like cl_event,
> >> > that the user is respo
Tom Stellard writes:
> On Thu, Jun 28, 2012 at 01:09:20AM +0200, Francisco Jerez wrote:
>> Tom Stellard writes:
>>
>> > We need to increment the reference count for objects, like cl_event,
>> > that the user is responsible for destroying when they are returned from
>> > the API. Otherwise, the
On Thu, Jun 28, 2012 at 01:09:20AM +0200, Francisco Jerez wrote:
> Tom Stellard writes:
>
> > We need to increment the reference count for objects, like cl_event,
> > that the user is responsible for destroying when they are returned from
> > the API. Otherwise, the object will be destroyed when
Tom Stellard writes:
> We need to increment the reference count for objects, like cl_event,
> that the user is responsible for destroying when they are returned from
> the API. Otherwise, the object will be destroyed when clover is done with
> it, even though the user will still have a reference
We need to increment the reference count for objects, like cl_event,
that the user is responsible for destroying when they are returned from
the API. Otherwise, the object will be destroyed when clover is done with
it, even though the user will still have a reference to it. For example:
1. clEnq
