7 Jun
2015
7 Jun
'15
12:10 a.m.
Hi Damien,
I found a minor issue with CCDocumentationGenerationTest>>pragmasMock declaring a
local variable “generator” with the same name as an instance variable. Pharo allows this
to compile (which it probably shouldn’t), but in GemStone we get a “variable has already
been defined” error.
It’s a simple fix, and I’m happy to make it if someone can give me write access to
PharoExtras. Otherwise, is this the right place to report this?
Cheers,
Jupiter
On 3 Jun 2015, at 7:26 pm, Damien Cassou
<damien.cassou(a)inria.fr> wrote:
Jupiter Jones <jupiter.jones(a)mail.com> writes:
you may want to spend time working on a flattening script instead of
flattening manually. This way, you can get the future pillar releases in
Gemstone as well.
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
another
approach would be to automatically flatten the traits in Pharo
before loading in Gemstone: see Behavior>>#flattenDownAllTraits.
Excellent - I’ll create a code base on GitHub with the traits
flattened and go from there.