Indeed both EGL 1.0 and EGL1.4 contain that language in the specs, but the Khronos manpage does not. I think we can safely ignore this.
Applications are very unlikely to rely on eglSwapBuffers failing in that case, and anyway the specification explicitly prohibits them from doing so by saying that the restriction may be lifted. It seems the intent of the specification is to say "implementations are allowed to only support surfaces bound to the current context; an unrestricted implementation is also possible, but applications must not rely on the restriction not being present". In this case, users of EGL_MESA_gallium would depend on not having the restriction, but that's OK because EGL_MESA_gallium guarantees that behavior. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
