search

KenzieMac130 / ogre-procedural

Automatically exported from code.google.com/p/ogre-procedural
0 stars 0 forks source link

Fix inconsistent naming #65

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
This project is named ogre-procedural. You use PROCEDURAL as the name of the 
suspected name in /usr/include/. You use OgreProcedural as the library name. 
This inconsistency is bad and makes me a very sad panda.

Please fix this inconsistency. I suggest using ogre-procedural everywhere 
because this is a lowercase unix-friendly name that also indicates its 
dependency on Ogre.

Original issue reported on code.google.com by svenst...@gmail.com on 24 Jul 2011 at 8:32

GoogleCodeExporter commented 8 years ago 
I've got to think about it, but namespace will probably not change, as it's 
already used in some user code, and "Procedural" is a lot less letters to write 
than "OgreProcedural" (some people don't use the "using" directive, thus 
writing a lot of namespaces in code)

Original comment by michael.broutin@gmail.com on 1 Aug 2011 at 9:05

GoogleCodeExporter commented 8 years ago 
The library is still at an early version, people will not expect it to be API 
stable.

Original comment by svenst...@gmail.com on 1 Aug 2011 at 9:14

GoogleCodeExporter commented 8 years ago

Original comment by michael.broutin@gmail.com on 1 Sep 2011 at 8:36

GoogleCodeExporter commented 8 years ago 
PROCEDURAL was changed to OgreProcedural everywhere in Cmake.

Original comment by michael.broutin@gmail.com on 3 Sep 2011 at 8:48

GoogleCodeExporter commented 8 years ago

Original comment by michael.broutin@gmail.com on 23 Oct 2011 at 3:39