beef up a couple of comments in example names.cc
authorCraig Dowell <craigdo@ee.washington.edu>
Fri, 30 Jan 2009 10:34:05 -0800
changeset 4152 99e350f3f7b4
parent 4151 682a4cae7a5f
child 4153 93bb91eae5cd
beef up a couple of comments in example names.cc
examples/names.cc
--- a/examples/names.cc	Fri Jan 30 10:30:07 2009 -0800
+++ b/examples/names.cc	Fri Jan 30 10:34:05 2009 -0800
@@ -87,7 +87,9 @@
   //
   // You can use the object names that you've assigned in calls to the Config
   // system to set Object Attributes.  For example, you can set the Mtu 
-  // Attribute of a Csma devices using the object naming service.
+  // Attribute of a Csma devices using the object naming service.  Note that 
+  // in this case, the "/Names" prefix is always required since the _Config_ 
+  // system always expects to see a fully qualified path name.
   //
   Config::Set ("/Names/client/eth0/Mtu", UintegerValue (1234));
 
@@ -98,6 +100,8 @@
   // to get to the server node, and then continue seamlessly adding named objects
   // in the path. This is not nearly as readable as the previous version, but it
   // illustrates how you can mix and match object names and Attribute names.
+  // Note that the config path now begins with a path in the "/NodeList" 
+  // namespace.
   //
   Config::Set ("/NodeList/1/eth0/Mtu", UintegerValue (1234));