On Fri, 7 May 2010 15:43:23 -0400, Kristian Høgsberg <[email protected]> wrote:
> Eeek, you're right. And this is different from the other cases > because here we don't actually delete the resource which caused > another resource to be added so we'll end up doing it again. I don't > have a good answer... we can leave it non-reentrant (didn't seem to > cause problems before, even when DRI1 apparently deleted resources > from the callback), or we can decide that the "add resource in > callback" case is not allowed. How about 'changing the resource database before returning FALSE is not allowed'? Otherwise, this function just returns and doesn't look at the DB again. All current users (dri, xfixes and xinerama) respect this requirement. So, I think we should just leave this function alone. -- [email protected]
pgpqmZPKElYQe.pgp
Description: PGP signature
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
