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

Roland Gude rol at ndgu.de
Sun Aug 26 08:29:39 EDT 2007

Ooops, i intended to send this to the mailinglist, not only to mr Eby.

-------- Weitergeleitete Nachricht --------
Von: Roland Gude <rol at ndgu.de>
An: Phillip J. Eby <pje at telecommunity.com>
Betreff: Re: [PEAK] a trellis based project - and perhaps an issues
Datum: Sat, 25 Aug 2007 12:54:22 +0200

Oh... i could have sworn the behaviour was undocumented. My apologies.
Still, i would include a warning that trellis.values(namme={}) leads to
a dictionary shared through multiple instances, as this might be a nasty
bug source, which is hard to reveal through unit-test etc. and is not
the behaviour i (as a first time user) would expect.

How about a section like 'traps' or 'common mistakes' which contains all
the donots for working with trellis?

Am Freitag, den 24.08.2007, 11:51 -0400 schrieb Phillip J. Eby:
> 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:
> http://peak.telecommunity.com/DevCenter/Trellis#automatic-activation-and-dependencies 
> """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:"""
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://www.eby-sarna.com/pipermail/peak/attachments/20070826/ad2a75de/attachment.bin

More information about the PEAK mailing list