Browse Source

correct comments

David Rose 23 years ago
parent
commit
4ecc489efc
3 changed files with 10 additions and 10 deletions
  1. 3 3
      dtool/Config.Irix.pp
  2. 4 4
      dtool/Config.Linux.pp
  3. 3 3
      dtool/Config.Win32.pp

+ 3 - 3
dtool/Config.Irix.pp

@@ -22,9 +22,9 @@
 
 
 // Will the compiler avoid inserting extra bytes in structs between a
 // Will the compiler avoid inserting extra bytes in structs between a
 // base struct and its derived structs?  It is safe to define this
 // base struct and its derived structs?  It is safe to define this
-// true if you don't know, but if you know that you can get away with
-// this you may gain a tiny performance gain by defining this false.
-// If you define this false incorrectly, you will get lots of
+// false if you don't know, but if you know that you can get away with
+// this you may gain a tiny performance gain by defining this true.
+// If you define this true incorrectly, you will get lots of
 // assertion failures on execution.
 // assertion failures on execution.
 #define SIMPLE_STRUCT_POINTERS
 #define SIMPLE_STRUCT_POINTERS
 
 

+ 4 - 4
dtool/Config.Linux.pp

@@ -22,11 +22,11 @@
 
 
 // Will the compiler avoid inserting extra bytes in structs between a
 // Will the compiler avoid inserting extra bytes in structs between a
 // base struct and its derived structs?  It is safe to define this
 // base struct and its derived structs?  It is safe to define this
-// true if you don't know, but if you know that you can get away with
-// this you may gain a tiny performance gain by defining this false.
-// If you define this false incorrectly, you will get lots of
+// false if you don't know, but if you know that you can get away with
+// this you may gain a tiny performance gain by defining this true.
+// If you define this true incorrectly, you will get lots of
 // assertion failures on execution.
 // assertion failures on execution.
-#define SIMPLE_STRUCT_POINTERS 1
+#define SIMPLE_STRUCT_POINTERS
 
 
 // Do we have a gettimeofday() function?
 // Do we have a gettimeofday() function?
 #define HAVE_GETTIMEOFDAY 1
 #define HAVE_GETTIMEOFDAY 1

+ 3 - 3
dtool/Config.Win32.pp

@@ -22,9 +22,9 @@
 
 
 // Will the compiler avoid inserting extra bytes in structs between a
 // Will the compiler avoid inserting extra bytes in structs between a
 // base struct and its derived structs?  It is safe to define this
 // base struct and its derived structs?  It is safe to define this
-// true if you don't know, but if you know that you can get away with
-// this you may gain a tiny performance gain by defining this false.
-// If you define this false incorrectly, you will get lots of
+// false if you don't know, but if you know that you can get away with
+// this you may gain a tiny performance gain by defining this true.
+// If you define this true incorrectly, you will get lots of
 // assertion failures on execution.
 // assertion failures on execution.
 #define SIMPLE_STRUCT_POINTERS 1
 #define SIMPLE_STRUCT_POINTERS 1