set var "TestingTestingTesting"set myArray($var) "This is a valuespanning multiple linesand containing several words...The array index holding this value also has several newlines"##or simpler:set myArray(line\ 1\nline\ 2) "Some\ndata..."

Statistics: Posted by nml375 — Fri Oct 30, 2009 3:47 pm

Statistics: Posted by willyw — Fri Oct 30, 2009 3:34 pm

Statistics: Posted by nml375 — Fri Oct 30, 2009 3:03 pm

proc saveArray {varname filename} {    upvar 1 $varname v    set fp [open $filename w]    foreach {name value} [array get v] {        puts $fp [list $name $value]    }    close $fp    return 0}proc restoreArray {varname filename} {    upvar 1 $varname v    set data ""    set fp [open $filename r]    while {![eof $fp]} {        set d [gets $fp]        if {[string length $d] != 0} {            append data $d        }    }    close $fp    array set v $data    return 0}

Statistics: Posted by arfer — Fri Oct 30, 2009 2:47 pm

proc saveArray {varname file} { upvar 1 $varname v set fp [open $file w] puts -nonewline $fp [array get v] close $fp}proc restoreArray {varname file} { upvar 1 $varname v set data "" set fp [open $file r] while {![eof $fp]} {  append data [read $fp] } close $fp array set v $data}

Statistics: Posted by nml375 — Fri Oct 30, 2009 1:27 pm

puts $fp list [array get $arr_name] 

Statistics: Posted by arfer — Fri Oct 30, 2009 2:50 am

proc join_greet {nick host hand chan} {  utimer 10 "puthelp \"PRIVMSG $chan :Hello $nick\""}

puthelp "PRIVMSG #thechannel :Hello Thenick"

proc join_greet {nick host hand chan] { utimer 10 [list puthelp "PRIVMSG $chan :Hello $nick"]}

Statistics: Posted by nml375 — Thu Oct 29, 2009 2:10 pm

Statistics: Posted by willyw — Thu Oct 29, 2009 1:58 pm

Just to pitch in;
The list command used in the first linked thread is not used to "protect" the output from array get. In fact, the list command will never see that output, instead it is used to avoid "double evaluation" when generating script code on the fly.

The most trivial form would be something as simple as this. In fact, it's a very stripped down version of the script posted by user in that thread, with no checks for the existance or type of the variable/array:

Code:

proc saveArray {varname file} { upvar 1 $varname v set fp [open $file w] puts $fp [list array set [array get $v]] close $fp}

This would then be restored by simply loading the generated file as a script (source thefile).

Statistics: Posted by willyw — Thu Oct 29, 2009 1:56 pm

Statistics: Posted by nml375 — Thu Oct 29, 2009 1:29 pm

I should have grouped together the arguments in the 'puts' command by placing them inside quotes.

Code:

proc pWriteArray {} {  global vDataArray  set id [open whatever.txt w]  foreach {name value} [array get vDataArray] {    puts $id "$name $value"  }  close $id  return 0}

Don't forget that I said the code is potentially incomplete. Eg. What do you want to happen if pWriteArray is called and vDataArray does not exist? The code is unfinished until you can account for every eventuality.

Statistics: Posted by willyw — Thu Oct 29, 2009 1:15 pm

proc saveArray {varname file} { upvar 1 $varname v set fp [open $file w] puts $fp [list array set $varname [array get v]] close $fp}

Statistics: Posted by nml375 — Thu Oct 29, 2009 12:55 pm

proc pWriteArray {} {  global vDataArray  set id [open whatever.txt w]  foreach {name value} [array get vDataArray] {    puts $id "$name $value"  }  close $id  return 0}

Statistics: Posted by arfer — Thu Oct 29, 2009 6:22 am

...
Similar difficulties would occur if one or more element name contains spaces (definitely not adviseable)

or if one or more element value contains spaces.

In those cases the saved text may not be an even number of 'words' representing name/value pairs and so would not readily read back into an array variable.

If the array element names do not contain spaces (as should normally be the case) and no array element value is an empty string (though only minor modification is needed to deal with this),

I would probably choose to save the data to a file as one array element per line. The first word in the line being the array element name and the remainder being the array element value. Something like the following (untested) :-

Code:

proc pReadArray {} {  global vDataArray  set id [open whatever.txt r]  set data [split [read -nonewline $id] \n]  foreach item $data {    set name [lindex [split $item] 0]    set value [join [lrange [split $item] 1 end]]    set vDataArray($name) $value  }  close $id  return 0}proc pWriteArray {} {  global vDataArray  set id [open whatever.txt w]  foreach {name value} [array get vDataArray] {    puts $id $name $value  }  close $id  return 0}

You would obviously call pReadArray to read in the data and populate the array vDataArray, and call pWriteArray to save the vDataArray name/value pairs to a text file.

Depending on exactly what the array names/values could contain, you might have to rethink things.

The code above is probably incomplete, even if it is correct for your needs. For example you might wish to test if the file exists before trying to read it etc etc.

Statistics: Posted by willyw — Thu Oct 29, 2009 1:15 am

proc pReadArray {} {  global vDataArray  set id [open whatever.txt r]  set data [split [read -nonewline $id] \n]  foreach item $data {    set name [lindex [split $item] 0]    set value [join [lrange [split $item] 1 end]]    set vDataArray($name) $value  }  close $id  return 0}proc pWriteArray {} {  global vDataArray  set id [open whatever.txt w]  foreach {name value} [array get vDataArray] {    puts $id $name $value  }  close $id  return 0}

Statistics: Posted by arfer — Wed Oct 28, 2009 9:45 pm