Prechádzať zdrojové kódy

Show core feature first in the API doc modules

Christophe Riccio 8 rokov pred
rodič
commit
23db2cd8b9
2 zmenil súbory, kde vykonal 22 pridanie a 22 odobranie
  1. 0 22
      glm/ext.hpp
  2. 22 0
      glm/glm.hpp

+ 0 - 22
glm/ext.hpp

@@ -1,28 +1,6 @@
 /// @file glm/ext.hpp
 ///
 /// @ref core (Dependence)
-/// 
-/// @defgroup gtc Stable extensions
-///
-/// @brief Additional features not specified by GLSL specification.
-/// 
-/// GTC extensions aim to be stable. 
-/// 
-/// Even if it's highly unrecommended, it's possible to include all the extensions at once by
-/// including <glm/ext.hpp>. Otherwise, each extension needs to be included  a specific file.
-/// 
-/// @defgroup gtx Experimental extensions
-/// 
-/// @brief Experimental features not specified by GLSL specification.
-/// 
-/// Experimental extensions are useful functions and types, but the development of
-/// their API and functionality is not necessarily stable. They can change 
-/// substantially between versions. Backwards compatibility is not much of an issue
-/// for them.
-/// 
-/// Even if it's highly unrecommended, it's possible to include all the extensions 
-/// at once by including <glm/ext.hpp>. Otherwise, each extension needs to be 
-/// included  a specific file.
 
 #include "detail/setup.hpp"
 

+ 22 - 0
glm/glm.hpp

@@ -48,6 +48,28 @@
 /// These templetes are implementation details of GLM types and should not be used explicitly.
 ///
 /// @ingroup core
+///
+/// @defgroup gtc Stable extensions
+///
+/// @brief Additional features not specified by GLSL specification.
+/// 
+/// GTC extensions aim to be stable. 
+/// 
+/// Even if it's highly unrecommended, it's possible to include all the extensions at once by
+/// including <glm/ext.hpp>. Otherwise, each extension needs to be included  a specific file.
+/// 
+/// @defgroup gtx Experimental extensions
+/// 
+/// @brief Experimental features not specified by GLSL specification.
+/// 
+/// Experimental extensions are useful functions and types, but the development of
+/// their API and functionality is not necessarily stable. They can change 
+/// substantially between versions. Backwards compatibility is not much of an issue
+/// for them.
+/// 
+/// Even if it's highly unrecommended, it's possible to include all the extensions 
+/// at once by including <glm/ext.hpp>. Otherwise, each extension needs to be 
+/// included  a specific file.
 
 #include "detail/_fixes.hpp"