Peder> For pure programming, the current path is fine. For
Peder> interactive use - which I personally do a lot during
Peder> development - the binary is a nuisance - for instance, in my
Peder> case, the "$s config" command used interactively fails to print
Peder> all the stuff that comes after the engineID option.
Tcl programming usually means a lot of interactive use and therefore I
am not really sure that using a binary representation for things like
engineID is a good idea.
Peder> What about an supplementing command, intended for interactive
Peder> use: $s configure-printable (or something shorter). Works like
Peder> $s configure, except that any binary strings are printed/parsed
Peder> as strings in hex encoding.
I do not like the idea of having multiple commands in the Tmn
extension for nearly the same thing, especially since you can easily
write a Tcl procedure which displays the output of $s configure in a
readable format. I prefer to have one command which returns data in a
format which works nicely in most of the cases. And probably getting
the engineID in hex rather than binary is what people need in most
cases...
Juergen
-- Juergen Schoenwaelder schoenw@ibr.cs.tu-bs.de http://www.cs.tu-bs.de/~schoenw Technical University Braunschweig, Dept. Operating Systems & Computer Networks Bueltenweg 74/75, 38106 Braunschweig, Germany. (Tel. +49 531 / 391 3289)-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.