back out unrelated changes
authorTom Henderson <tomh@tomh.org>
Sat, 13 Oct 2007 15:10:23 -0700
changeset 1781 93e25aba0e79
parent 1780 d76cc3437a41
child 1782 444ef6129d2e
back out unrelated changes
examples/wscript
src/common/packet.h
src/core/object.cc
--- a/examples/wscript	Sat Oct 13 15:06:35 2007 -0700
+++ b/examples/wscript	Sat Oct 13 15:10:23 2007 -0700
@@ -18,10 +18,6 @@
         ['csma', 'internet-node'])
     obj.source = 'csma-one-subnet.cc'
 
-    obj = bld.create_ns3_program('george',
-        ['csma', 'internet-node'])
-    obj.source = 'george.cc'
-
     obj = bld.create_ns3_program('udp-echo',
         ['csma', 'internet-node'])
     obj.source = 'udp-echo.cc'
--- a/src/common/packet.h	Sat Oct 13 15:06:35 2007 -0700
+++ b/src/common/packet.h	Sat Oct 13 15:10:23 2007 -0700
@@ -243,16 +243,6 @@
   /**
    * A packet is allocated a new uid when it is created
    * empty or with zero-filled payload.
-   * 
-   * Note:  This uid is an internal uid and cannot be counted on to 
-   * provide an accurate counter of how many "simulated packets" of a 
-   * particular protocol are in the system.  It is not trivial to make
-   * this uid into such a counter, because of questions such as what
-   * should the uid be when the packet is sent over broadcast media, or
-   * when fragmentation occurs.  If a user wants to trace actual packet
-   * counts, he or she should look at e.g. the IP ID field or transport
-   * sequence numbers, or other packet or frame counters at other 
-   * protocol layers.
    *
    * \returns an integer identifier which uniquely
    *          identifies this packet.
--- a/src/core/object.cc	Sat Oct 13 15:06:35 2007 -0700
+++ b/src/core/object.cc	Sat Oct 13 15:10:23 2007 -0700
@@ -197,7 +197,6 @@
   do {
     NS_ASSERT (currentObject != 0);
     InterfaceId cur = currentObject->m_iid;
-    NS_LOG_LOGIC("In Loop: " << cur.GetName());
     while (cur != iid && cur != Object::iid)
       {
         cur = InterfaceId::LookupParent (cur);