Use a namespace to keep apart implementations of network handlers

Since we'll have three "InventoryHandler" classes, etc. this shows an
example of how we can compile with all of them at the same time using
namespaces. We'll have:

Net::InventoryHandler     - the interface
EAthena::InventoryHandler - the eAthena implementation
TmwServ::InventoryHandler - the tmwserv implementation

Maybe we'll find a better way later, but for now this works. I'm not
convinced yet that using namespaces is better than just using longer
class names like EAthenaInventoryHandler.

2 files changed, 8 insertions, 0 deletions

diff --git a/src/net/tmwserv/inventoryhandler.cpp b/src/net/tmwserv/inventoryhandler.cpp
index cedeb465..f21c25a9 100644
--- a/src/net/tmwserv/inventoryhandler.cpp
+++ b/src/net/tmwserv/inventoryhandler.cpp
@@ -37,6 +37,8 @@
 
 #include "resources/iteminfo.h"
 
+namespace TmwServ {
+
 Net::InventoryHandler *inventoryHandler;
 
 InventoryHandler::InventoryHandler()
@@ -123,3 +125,5 @@ void InventoryHandler::moveItem(StorageType source, int slot, int amount,
 {
     // TODO
 }
+
+} // namespace TmwServ
diff --git a/src/net/tmwserv/inventoryhandler.h b/src/net/tmwserv/inventoryhandler.h
index 5dd788ef..38281e2a 100644
--- a/src/net/tmwserv/inventoryhandler.h
+++ b/src/net/tmwserv/inventoryhandler.h
@@ -25,6 +25,8 @@
 #include "net/inventoryhandler.h"
 #include "net/messagehandler.h"
 
+namespace TmwServ {
+
 class InventoryHandler : public MessageHandler, Net::InventoryHandler
 {
     public:
@@ -52,4 +54,6 @@ class InventoryHandler : public MessageHandler, Net::InventoryHandler
 
 extern Net::InventoryHandler *inventoryHandler;
 
+} // namespace TmwServ
+
 #endif