[Bf-blender-cvs] [66d81bd] soc-2014-viewport_context: edited glew-mx documentation (this history is going to get squashed anyway right?)

Jason Wilkins noreply at git.blender.org
Sat Jul 26 20:42:21 CEST 2014


Commit: 66d81bd0da1b8492a7d95246f1364b28396694be
Author: Jason Wilkins
Date:   Sat Jul 26 13:38:41 2014 -0500
Branches: soc-2014-viewport_context
https://developer.blender.org/rB66d81bd0da1b8492a7d95246f1364b28396694be

edited glew-mx documentation (this history is going to get squashed anyway right?)

===================================================================

M	intern/glew-mx/intern/glew-mx.c

===================================================================

diff --git a/intern/glew-mx/intern/glew-mx.c b/intern/glew-mx/intern/glew-mx.c
index e82a03a..b216eb3 100644
--- a/intern/glew-mx/intern/glew-mx.c
+++ b/intern/glew-mx/intern/glew-mx.c
@@ -29,7 +29,8 @@
  *  \ingroup glew-mx
  *
  * Support for GLEW Multimple rendering conteXts (MX)
- * 
+ * Maintained by Jason Wilkins
+ *
  * Different rendering contexts may have different entry points 
  * to extension functions of the same name.  So it can cause
  * problems if, for example, a second context uses a pointer to
@@ -38,10 +39,11 @@
  * GLEW has basic support for multiple contexts by enabling GLEW_MX,
  * but it does not provide a full implementation.  This is because
  * there are too many questions about thread safety and memory
- * allocation that are up to the user of the library.
+ * allocation that are up to the user of GLEW.
  *
  * This implementation is very basic.  It is not thread safe and it
- * uses malloc.
+ * uses malloc. For a single context the overhead should be
+ * no more than using GLEW without GLEW_MX enabled.
  */
 
 #ifdef GLEW_MX




More information about the Bf-blender-cvs mailing list