Commit 68e16e48 authored by Shashi Guruprasad's avatar Shashi Guruprasad

removed syntax check with nse. It will reappear as a second parsing stage

after assign
parent 57e0d825
......@@ -416,14 +416,6 @@ proc parse_delay {dspec} {
# We now have all our infrastructure in place. We are ready to load
# the NS file.
# We first run the script through NSE to check syntax errors
if { ${GLOBALS::disablense} != 1 } {
file copy -force ${GLOBALS::nstbcompat} tb_compat.tcl
if { [catch {exec nse ${GLOBALS::nsfile}} errMsg] == 1 } {
perror "Syntax check with NS failed\nerrorcode: $errorCode\n error msg: $errMsg"
}
}
if { ${GLOBALS::errors} != 1 } {
file copy -force ${GLOBALS::tbcompat} .
source ${GLOBALS::nsfile}
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment