[Seaside-dev] Issue 313 in seaside: Allow platforms to use an
instance variable to cache objects in WAFileLibrary
Dale Henrichs
dale.henrichs at gemstone.com
Fri Jan 30 00:35:00 UTC 2009
----- "Randal L. Schwartz" <merlyn at stonehenge.com> wrote:
| >>>>> "codesite-noreply" == codesite-noreply
| <codesite-noreply at google.com> writes:
|
| codesite-noreply> Comment #10 on issue 313 by da... at teleport.com:
| Allow platforms to use an
| codesite-noreply> instance variable to cache objects in WAFileLibrary
| codesite-noreply>
| http://code.google.com/p/seaside/issues/detail?id=313
|
| codesite-noreply> GemStone uses #[...] as the array constructor:
|
| codesite-noreply> #[ expression, expression, expression, ... ]
|
| So that would make it like Squeak's { ... },
| which GemStone has also adopted? :)
|
Correct,
{ expression. expression. expression. ... } returns same result as
#[ expression, expression, expression, ... ] an Array.
The #[...] was kept for legacy code. We hadn't used {} for an incompatible purpose yet:)
Like I said, we need more characters.
Dale
More information about the seaside-dev
mailing list