diff options
author | Jeff Ames | 2008-05-16 01:22:11 +0000 |
---|---|---|
committer | Jeff Ames | 2008-05-16 01:22:11 +0000 |
commit | 65c5efe43b68700bad94076d4cd421160203c5de (patch) | |
tree | 589b56649ed02f4942671fd6e51c6dc43f682e0d /OpenSim/Region/Physics/Manager/ZeroMesher.cs | |
parent | Thank you very much, mjm for : (diff) | |
download | opensim-SC-65c5efe43b68700bad94076d4cd421160203c5de.zip opensim-SC-65c5efe43b68700bad94076d4cd421160203c5de.tar.gz opensim-SC-65c5efe43b68700bad94076d4cd421160203c5de.tar.bz2 opensim-SC-65c5efe43b68700bad94076d4cd421160203c5de.tar.xz |
Formatting cleanup.
Diffstat (limited to '')
-rw-r--r-- | OpenSim/Region/Physics/Manager/ZeroMesher.cs | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/OpenSim/Region/Physics/Manager/ZeroMesher.cs b/OpenSim/Region/Physics/Manager/ZeroMesher.cs index b98cb35..b759213 100644 --- a/OpenSim/Region/Physics/Manager/ZeroMesher.cs +++ b/OpenSim/Region/Physics/Manager/ZeroMesher.cs | |||
@@ -31,9 +31,9 @@ using OpenSim.Framework; | |||
31 | /* | 31 | /* |
32 | * This is the zero mesher. | 32 | * This is the zero mesher. |
33 | * Whatever you want him to mesh, he can't, telling you that by responding with a null pointer. | 33 | * Whatever you want him to mesh, he can't, telling you that by responding with a null pointer. |
34 | * Effectivly this is for switching off meshing and for testing as each physics machine should deal | 34 | * Effectivly this is for switching off meshing and for testing as each physics machine should deal |
35 | * with the null pointer situation. | 35 | * with the null pointer situation. |
36 | * But it's also a convenience thing, as physics machines can rely on having a mesher in any situation, even | 36 | * But it's also a convenience thing, as physics machines can rely on having a mesher in any situation, even |
37 | * if it's a dump one like this. | 37 | * if it's a dump one like this. |
38 | * Note, that this mesher is *not* living in a module but in the manager itself, so | 38 | * Note, that this mesher is *not* living in a module but in the manager itself, so |
39 | * it's always availabe and thus the default in case of configuration errors | 39 | * it's always availabe and thus the default in case of configuration errors |