[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: address format changing hasn't completed? (fwd)



On Wed, 3 Nov 1999, Nader Salehi wrote:

> Guo,
> 
> You should not have a problem.  The addr_ variables in the Tcl files
> you mention point to node addresses.  If an addr_ is part of an agent,

I still don't get it, in line 456 of route-proto.tcl, there's following
statement:
    $proto($node) add-peer $nbr [$rtproto set addr_]
To my knowledge, here addr_ should be the variable of $rtproto, which
is an routing agent (DV).

> it is bound to here_.addr_ of the associated C++ shadow object.

where's this "bind" called? I only find it in mip.cc, not in agent.cc.

> 
> Nader
> 

Thanks.

But even running a simple simulation like .../ex/simple-rtg.tcl, you'll
get the following messages:

can't read "addr_": no such variable
    while executing
"subst $[subst $var]"
    (procedure "_o115" line 5)
    (Object next line 5)
    invoked from within
"_o115 next addr_"
    ("eval" body line 1)
    invoked from within
"eval $self next $args"
    (procedure "_o115" line 18)
    (Agent set line 18)
    invoked from within
"$rtproto set addr_"
    (procedure "Agent/rtProto/DV" line 18)
    (Agent/rtProto/DV init-all line 18)
    invoked from within
"Agent/rtProto/DV init-all"
    ("eval" body line 1)
    invoked from within
"eval Agent/rtProto/$proto init-all $rtprotos_($proto)"
    (procedure "_o96" line 5)
    (RouteLogic configure line 5)
    invoked from within
"[$self get-routelogic] configure"
    (procedure "_o3" line 5)
    (Simulator run line 5)
    invoked from within
"$ns run"
    (file "simple-rtg.tcl" line 80)




I think the problem is related to the "addr_" variable.