egghelp/eggheads community

variable backup in file..

2003-06-05T20:19:46-04:00

In tcl, there are no multidimensional arrays. When you say blah(word1,word2) that is actually a single entry called "word1,word2", which is a perfectly valid name. If you say blah(word1) it will not return a new array (as a real multidimensional array would).

Anyway, I'll go ahead and update this code a bit, this should work, although I haven't tested it:

Code:

proc write_array {name file} {   set fp [open $file w]   puts $fp [uplevel 1 [list array get $name]]  close $fp } proc read_array {name file} {   set fp [open $file r]   uplevel 1 [list array set $name [read -nonewline $fp]]  close $fp }

Statistics: Posted by stdragon — Thu Jun 05, 2003 8:19 pm

variable backup in file..

2003-06-05T10:42:25-04:00

does this also work for multiple arrays (like myvar(name,date)) ?

Statistics: Posted by GodOfSuicide — Thu Jun 05, 2003 10:42 am

variable backup in file..

2003-06-03T16:49:19-04:00

True.

However, namespaces and the upvar commands are the two I am trying to work on, upvar I have never had use for.

Statistics: Posted by ppslim — Tue Jun 03, 2003 4:49 pm

variable backup in file..

2003-06-03T15:48:32-04:00

ppslim give me some credit! I think you misunderstood what I said. Uplevel works just like eval, right? So it's not very safe to read in text and simply eval it. If there is a stray line with [blah blah] it will try to execute it. Now, if the person *only* uses write_array to write the file, it's not too bad, because it will escape those characters.

That said, I just realized the code doesn't even work. The 'array set' command expects a list as a single variable, e.g.

. The code as stated, since it evaluates the *result* of [read] rather than the [read] itself, will make each thing a separate argument rather than a list element. This will call the command with too many arguments.

Perhaps I have been away too long if you've forgotten to put such things in a
- construct rather than just quotes :) This is the same sort of problem that occurs when people say utimer "putserv $blah" rather than utimer [list putserv $blah].
  
  Anyway, it's easier and more efficient to use the upvar command rather than have tcl create all these lists.

Statistics: Posted by stdragon — Tue Jun 03, 2003 3:48 pm

variable backup in file..

2003-06-03T15:19:27-04:00

No, thats why I used quotes and not brackets.

Damn, you can't have been away that long

Statistics: Posted by ppslim — Tue Jun 03, 2003 3:19 pm

variable backup in file..

2003-06-03T15:14:31-04:00

ppslim, one problem with your code: in read_array you're passing the result of [read] to uplevel to be evaluated (since you used quotes). Maybe a better way is to use upvar?

Statistics: Posted by stdragon — Tue Jun 03, 2003 3:14 pm

variable backup in file..

2003-06-03T14:42:59-04:00

Tcl arrays (they are infact hash lists) can be written to file easily.

Code:

proc write_array {name file} {  set fp [open $file w]  puts $fp [uplevel 1 "array get $name"]  close $fp}proc read_array {name file} {  set fp [open $file r]  uplevel 1 "array set $name [read -nonewline $fp]"  close $fp}

Statistics: Posted by ppslim — Tue Jun 03, 2003 2:42 pm

variable backup in file..

2003-06-03T12:50:54-04:00

Hi..

i've got a quite big var (array), and i'd need to backup cos this data is lost if the bot crashes / restarts / etc

if there a way to write a var into a file and write it back again ?
like delphi

Code:

write :for i := 0 to my_array.items.count -1 do my_memo.lines.add(my_array.item[i])get :for i := 0 to my_memo.lines.count -1 do my_array.item[i] := memo1.lines[i]

The array isn't myvar(1) myvar(2) but myvar(word) myvar(anotherword) and so on.

I'd like to dump this var into a txt file and if the bot restarts it should write the var based onto the data in this txt.

Statistics: Posted by GodOfSuicide — Tue Jun 03, 2003 12:50 pm