summaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.python/py-connection.exp
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2022-11-14 14:12:07 +0000
committerAndrew Burgess <aburgess@redhat.com>2022-11-28 21:04:09 +0000
commitb0e16ca58d444a2b6dc2b4f71081d6c761d9712e (patch)
tree6f3af4fedeec1f145b20267e39646100d8f384c7 /gdb/testsuite/gdb.python/py-connection.exp
parent95701caeadd48415b3cb3d7fc7d9a4ef84211c55 (diff)
downloadbinutils-gdb-b0e16ca58d444a2b6dc2b4f71081d6c761d9712e.tar.gz
gdb/testsuite: remove use of then keyword from gdb.python/*.exp
The canonical form of 'if' in modern TCL is 'if {} {}'. But there's still a bunch of places in the testsuite where we make use of the 'then' keyword, and sometimes these get copies into new tests, which just spreads poor practice. This commit removes all use of the 'then' keyword from the gdb.python/ test script directory. There should be no changes in what is tested after this commit.
Diffstat (limited to 'gdb/testsuite/gdb.python/py-connection.exp')
-rw-r--r--gdb/testsuite/gdb.python/py-connection.exp2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.python/py-connection.exp b/gdb/testsuite/gdb.python/py-connection.exp
index 91315eb1af4..fc212fc09c0 100644
--- a/gdb/testsuite/gdb.python/py-connection.exp
+++ b/gdb/testsuite/gdb.python/py-connection.exp
@@ -29,7 +29,7 @@ if { [prepare_for_testing "failed to prepare" ${testfile} ${srcfile}] } {
# Skip all tests if Python scripting is not enabled.
if { [skip_python_tests] } { continue }
-if ![runto_main] then {
+if {![runto_main]} {
return 0
}