[Prototype-core] Re: event memo modified is evaluated to false

2010-03-26 Thread Tobie Langel
The reason for this design choice was to avoid the following altogether: if (event.memo) { foo = event.memo.foo; } and allow this instead: foo = event.memo.foo; There are memory costs involved with this design choice, but these can easily be mitigated by passing in a value to

Re: [Prototype-core] Re: event memo modified is evaluated to false

2010-03-26 Thread Christophe Porteneuve
Tobie, If that's so, then we should explictly forbid memo not being an object, shoudln't we? Or at least make this crystal-clear in the docs. The current docs only state memo: metadata for the event. Otherwise, you can pull my commit b1bfdd5, fresh off the current main master :-) Le