[PEAK] a trellis based project - and perhaps an issues

Phillip J. Eby pje at telecommunity.com
Fri Aug 24 11:51:19 EDT 2007

At 04:26 PM 8/24/2007 +0200, Roland Gude wrote:
>even though it is not a big deal, it is something one has to keep in
>mind when creating trellis.Components. And i think it is something that
>should be mentioned in the documentation.

Actually, it is, complete with an example that follows the same pattern, under:


"""A rule like this will return the same object every time, because 
it doesn't use any other cells to compute its value. So it runs once, 
and never again. If we also defined a trellis.value for aDict, then 
the attribute would also be writable, and we could put a different 
value there. But since we didn't, it becomes read-only:"""

More information about the PEAK mailing list