[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ESPResSo-devel] blockfile
From: |
Ulf Schiller |
Subject: |
Re: [ESPResSo-devel] blockfile |
Date: |
Mon, 27 Aug 2007 13:57:18 +0200 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.12) Gecko/20050921 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Limbach, Hans Joerg, LAUSANNE, NRC-FS wrote:
> Hi,
>
> Can somebody explain me why
> blockfile channel write variable box_l
> works, but
> blockfile channel write variable { box_l }
> not. And finally
> blockfile channel write variable { box_l time_step }
> again works.
>
> I guess it is some secret (at least for me) of tcl that causes this. And
> I also guess it should be explained in the ug at some point.
I think it's a combination between the implementation of the
blockfile_write_variable procedure and TLC's handling of lists.
If the list of variables to be written is a list of length one, it is
directly passed to the setmd command. The difference between box_l and
{ box_l } boils down to the difference of the strings "box_l" and
" box_l ", which suggests that
blockfile channel write variable {box_l}
works, and it does.
If the list is longer it is processed by foreach and the elements are
successively passed to setmd. One may also consider this a bug in the
implementation of blockfile_write_variable.
Does anybody remember whether there was a reason that it is implemented
this way (besides formatting output nicely)?
Regards,
Ulf
- --
Ulf D. Schiller * Room 1.404 * Phone +49 6131 379-481
Max Planck Institute for Polymer Research
Theory Group
D-55128 Mainz, Germany 50° 0' N, 008° 16' E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFG0rwbtqL0QpvXQjERAg+iAKDT/XHTB2nJRuEdYu74ykvGV0gJYACgrRLO
MzWHgL+Dg48OTRPC5xleiB8=
=2Pwj
-----END PGP SIGNATURE-----