Jeff Vigil

https://www.khronos.org/registry/EGL/extensions/KHR/EGL_KHR_display_reference.txt - is not sufficient then? We had a lot of discussion at one time for that. Just curious, who is part of this EXT?

Sorry my comment was not push back. I got a better read and I get it.

Not sure if rebasing on other work in progress has turned out without issue. Not sure.

Please add other reviewers. Jon and I can says its well formed, but +1 from experts is reassuring.

When you say "private" EGL_PRIVATE_DISPLAY_EXT, private to what? Is this private to a single thread (TLS space for implementation)? or private by some other context? That would need to be...

I just wanted to be sure that it wasn't private to a thread. eglGetPlatformDisplay" with EGL_PRIVATE_DISPLAY_EXT set EGL_TRUE - will not return the same EGLDisplay handle twice, so private by...

Looking at your current EGL_EXT_display_alloc.txt lines 62-64 Good Line 88, may I suggest add "unique" handle. That might cover James' suggestion and would cover my desire for clarity for users...

PRIVATE is OK with me. In all cases what that means needs to be clear.

@oddhack can you review this?

What critsec described is reality. Unfortunately you can't infer Android specific behavior from this interpretation. Sorry can't give you a more useful answer. Closing.