Can I use the same variable name for different scripts?

[daigo]

I am running all scripts on one eggdrop bot. Is it okay for me to use the same variable name if they are in different scripts? For instance, if I have this line in one script:

Code: Select all

set txt [string tolower $txt]

Can I use the same line of code in another script? Or do I have to change

Code: Select all

txt

to something else?

[SpiKe^^]

An Eggdrop bot can have only One Global Variable named txt

Usually txt is used in a proc, and that would be a local variable.
In most cases, local variables do not interfere with global variables.

[willyw]

You might like to read:

http://forum.egghelp.org/viewtopic.php?t=12900

[daigo]

You might like to read:

http://forum.egghelp.org/viewtopic.php?t=12900

The article says to use

Code: Select all

bind pub - "hi" MyScript::respond 

in their example. What is the difference between using this and

Code: Select all

bind pub - "hi" ::MyScript::respond 

?

[caesar]

My guess is that the difference is that in the second the respond proc is inside the MyScript namespace.

[daigo]

My guess is that the difference is that in the second the respond proc is inside the MyScript namespace.

Both of them are inside the MyScript namespace (I'm looking at another script that uses the double colons before the MyScript bind). What's interesting is, this script I'm looking at uses global. Here is the script:

Code: Select all

namespace eval magic8ball {

variable 8ballCatch "!8ball"

proc 8ball {nick host handle channel arg} {
  global 8ballCatch
  set cmd [string tolower [lindex $arg 0]]

  if {[file exists /eggdrop/scripts/8ball.txt]} {
    set list [open /eggdrop/scripts/8ball.txt r]
    set reply ""
    while {![eof $list]} {
      set tmp [gets $list]
      set reply [lappend test [string trim $tmp]]
    }
    close $list
  }
  set number [rand [expr [llength $reply] + 1]]
  puthelp "PRIVMSG $channel :8-ball\: [lindex $reply $number]"
}
bind pub - $8ballCatch ::magic8ball::8ball
}

[CrazyCat]

I think that the utility of the lead :: is essentialy when you use the import/export.
And it might be a little bit faster for the tcl to use the full path (::namespace::procedure) than looking in the namespace for the existence of a sub-namespace and then looking in global.