[Seaside-dev] Issue 313 in seaside: Allow platforms to use an instance variable to cache objects in WAFileLibrary

codesite-noreply at google.com codesite-noreply at google.com
Sun Feb 1 15:37:28 UTC 2009


Comment #12 on issue 313 by WeybridgeWay: Allow platforms to use an  
instance variable to cache objects in WAFileLibrary
http://code.google.com/p/seaside/issues/detail?id=313

For consistency and simplicity of the code, I'm in favor of removing the  
caching entirely. On the other hand, this
issue started because WAFileLibraryTest>>#'testCompileByteArray' insisted  
that two calls to the method return
the identical object. A less complete work-around is for other platforms to  
implement Array>>#'beMutable' as
     ^self copy
and then remove the test for identical results. This would be a less  
complete (and also less intrusive) solution.
I'm happy to take on either task (though might need some guidance on  
removing the caching entirely).
--James

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings


More information about the seaside-dev mailing list