Startup Error: SyntaxErrorNotification: Cannot store into
This this started at 29th and crashes image while loading configuration. Any idea whatâs wrong? ==== Startup Error: SyntaxErrorNotification: Cannot store into OCSemanticError>>notify:at: OCSemanticError>>defaultAction [ :ex | ex defaultAction. ^ self compilationContext failBlock value ] in OpalCompiler>>doSemanticAnalysis in Block: [ :ex | ... BlockClosure>>cull: [ self exceptionHandlerBlock cull: exception ] in Context>>handleSignal: in Block: [ self exceptionHandlerBlock cull: exception ] BlockClosure>>ensure: Context>>handleSignal: OCSemanticError(Exception)>>signal OCASTSemanticAnalyzer>>storeIntoSpecialVariable: OCASTSemanticAnalyzer>>lookupVariableForWrite: OCASTSemanticAnalyzer>>visitAssignmentNode: RBAssignmentNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: [ :each | self visitNode: each ] in OCASTSemanticAnalyzer>>visitSequenceNode: in Block: [ :each | self visitNode: each ] OrderedCollection>>do: OCASTSemanticAnalyzer>>visitSequenceNode: RBSequenceNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: OCASTSemanticAnalyzer>>visitMethodNode: RBMethodNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: OCASTSemanticAnalyzer>>analyze: RBMethodNode>>doSemanticAnalysis RBMethodNode>>doSemanticAnalysisInContext: [ ast doSemanticAnalysisInContext: self compilationContext ] in OpalCompiler>>doSemanticAnalysis in Block: [ ast doSemanticAnalysisInContext: self compilatio...etc... BlockClosure>>on:do: OpalCompiler>>doSemanticAnalysis [ ast := self parse. self doSemanticAnalysis ] in [ [ ast := self parse. self doSemanticAnalysis ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... BlockClosure>>on:do: [ [ ast := self parse. self doSemanticAnalysis ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... Got startup errors: SyntaxErrorNotification: Cannot store into Cheers Uko
On 01 Sep 2014, at 17:35, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
This this started at 29th and crashes image while loading configuration. Any idea whatâs wrong?
This means that you load code that assigns to arguments (method arguments). The new compiler allowed it (an oversight), the old one did notâ¦. now it is again not allowed. (for bock arguments, it is still allowed).
==== Startup Error: SyntaxErrorNotification: Cannot store into OCSemanticError>>notify:at: OCSemanticError>>defaultAction [ :ex | ex defaultAction. ^ self compilationContext failBlock value ] in OpalCompiler>>doSemanticAnalysis in Block: [ :ex | ... BlockClosure>>cull: [ self exceptionHandlerBlock cull: exception ] in Context>>handleSignal: in Block: [ self exceptionHandlerBlock cull: exception ] BlockClosure>>ensure: Context>>handleSignal: OCSemanticError(Exception)>>signal OCASTSemanticAnalyzer>>storeIntoSpecialVariable: OCASTSemanticAnalyzer>>lookupVariableForWrite: OCASTSemanticAnalyzer>>visitAssignmentNode: RBAssignmentNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: [ :each | self visitNode: each ] in OCASTSemanticAnalyzer>>visitSequenceNode: in Block: [ :each | self visitNode: each ] OrderedCollection>>do: OCASTSemanticAnalyzer>>visitSequenceNode: RBSequenceNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: OCASTSemanticAnalyzer>>visitMethodNode: RBMethodNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: OCASTSemanticAnalyzer>>analyze: RBMethodNode>>doSemanticAnalysis RBMethodNode>>doSemanticAnalysisInContext: [ ast doSemanticAnalysisInContext: self compilationContext ] in OpalCompiler>>doSemanticAnalysis in Block: [ ast doSemanticAnalysisInContext: self compilatio...etc... BlockClosure>>on:do: OpalCompiler>>doSemanticAnalysis [ ast := self parse. self doSemanticAnalysis ] in [ [ ast := self parse. self doSemanticAnalysis ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... BlockClosure>>on:do: [ [ ast := self parse. self doSemanticAnalysis ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... Got startup errors: SyntaxErrorNotification: Cannot store into
Cheers Uko
Thanks Marcus! On 01 Sep 2014, at 17:45, Marcus Denker <marcus.denker@inria.fr> wrote:
On 01 Sep 2014, at 17:35, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
This this started at 29th and crashes image while loading configuration. Any idea whatâs wrong?
This means that you load code that assigns to arguments (method arguments). The new compiler allowed it (an oversight), the old one did notâ¦. now it is again not allowed.
(for bock arguments, it is still allowed).
==== Startup Error: SyntaxErrorNotification: Cannot store into OCSemanticError>>notify:at: OCSemanticError>>defaultAction [ :ex | ex defaultAction. ^ self compilationContext failBlock value ] in OpalCompiler>>doSemanticAnalysis in Block: [ :ex | ... BlockClosure>>cull: [ self exceptionHandlerBlock cull: exception ] in Context>>handleSignal: in Block: [ self exceptionHandlerBlock cull: exception ] BlockClosure>>ensure: Context>>handleSignal: OCSemanticError(Exception)>>signal OCASTSemanticAnalyzer>>storeIntoSpecialVariable: OCASTSemanticAnalyzer>>lookupVariableForWrite: OCASTSemanticAnalyzer>>visitAssignmentNode: RBAssignmentNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: [ :each | self visitNode: each ] in OCASTSemanticAnalyzer>>visitSequenceNode: in Block: [ :each | self visitNode: each ] OrderedCollection>>do: OCASTSemanticAnalyzer>>visitSequenceNode: RBSequenceNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: OCASTSemanticAnalyzer>>visitMethodNode: RBMethodNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: OCASTSemanticAnalyzer>>analyze: RBMethodNode>>doSemanticAnalysis RBMethodNode>>doSemanticAnalysisInContext: [ ast doSemanticAnalysisInContext: self compilationContext ] in OpalCompiler>>doSemanticAnalysis in Block: [ ast doSemanticAnalysisInContext: self compilatio...etc... BlockClosure>>on:do: OpalCompiler>>doSemanticAnalysis [ ast := self parse. self doSemanticAnalysis ] in [ [ ast := self parse. self doSemanticAnalysis ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... BlockClosure>>on:do: [ [ ast := self parse. self doSemanticAnalysis ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... Got startup errors: SyntaxErrorNotification: Cannot store into
Cheers Uko
By the way, is there any way to check which is the problematic method? Because I failed to find it in log. Uko On 01 Sep 2014, at 17:45, Marcus Denker <marcus.denker@inria.fr> wrote:
On 01 Sep 2014, at 17:35, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
This this started at 29th and crashes image while loading configuration. Any idea whatâs wrong?
This means that you load code that assigns to arguments (method arguments). The new compiler allowed it (an oversight), the old one did notâ¦. now it is again not allowed.
(for bock arguments, it is still allowed).
==== Startup Error: SyntaxErrorNotification: Cannot store into OCSemanticError>>notify:at: OCSemanticError>>defaultAction [ :ex | ex defaultAction. ^ self compilationContext failBlock value ] in OpalCompiler>>doSemanticAnalysis in Block: [ :ex | ... BlockClosure>>cull: [ self exceptionHandlerBlock cull: exception ] in Context>>handleSignal: in Block: [ self exceptionHandlerBlock cull: exception ] BlockClosure>>ensure: Context>>handleSignal: OCSemanticError(Exception)>>signal OCASTSemanticAnalyzer>>storeIntoSpecialVariable: OCASTSemanticAnalyzer>>lookupVariableForWrite: OCASTSemanticAnalyzer>>visitAssignmentNode: RBAssignmentNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: [ :each | self visitNode: each ] in OCASTSemanticAnalyzer>>visitSequenceNode: in Block: [ :each | self visitNode: each ] OrderedCollection>>do: OCASTSemanticAnalyzer>>visitSequenceNode: RBSequenceNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: OCASTSemanticAnalyzer>>visitMethodNode: RBMethodNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: OCASTSemanticAnalyzer>>analyze: RBMethodNode>>doSemanticAnalysis RBMethodNode>>doSemanticAnalysisInContext: [ ast doSemanticAnalysisInContext: self compilationContext ] in OpalCompiler>>doSemanticAnalysis in Block: [ ast doSemanticAnalysisInContext: self compilatio...etc... BlockClosure>>on:do: OpalCompiler>>doSemanticAnalysis [ ast := self parse. self doSemanticAnalysis ] in [ [ ast := self parse. self doSemanticAnalysis ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... BlockClosure>>on:do: [ [ ast := self parse. self doSemanticAnalysis ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... Got startup errors: SyntaxErrorNotification: Cannot store into
Cheers Uko
which configuration are you trying to load? 2014-09-01 18:20 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk@me.com>:
By the way, is there any way to check which is the problematic method? Because I failed to find it in log.
Uko
On 01 Sep 2014, at 17:45, Marcus Denker <marcus.denker@inria.fr> wrote:
On 01 Sep 2014, at 17:35, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
This this started at 29th and crashes image while loading configuration. Any idea whatâs wrong?
This means that you load code that assigns to arguments (method arguments). The new compiler allowed it (an oversight), the old one did notâ¦. now it is again not allowed.
(for bock arguments, it is still allowed).
==== Startup Error: SyntaxErrorNotification: Cannot store intoOCSemanticError>>notify:at: OCSemanticError>>defaultAction [ :ex | ex defaultAction. ^ self compilationContext failBlock value ] in OpalCompiler>>doSemanticAnalysis in Block: [ :ex | ... BlockClosure>>cull: [ self exceptionHandlerBlock cull: exception ] in Context>>handleSignal: in Block: [ self exceptionHandlerBlock cull: exception ] BlockClosure>>ensure: Context>>handleSignal: OCSemanticError(Exception)>>signal OCASTSemanticAnalyzer>>storeIntoSpecialVariable: OCASTSemanticAnalyzer>>lookupVariableForWrite: OCASTSemanticAnalyzer>>visitAssignmentNode: RBAssignmentNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: [ :each | self visitNode: each ] in OCASTSemanticAnalyzer>>visitSequenceNode: in Block: [ :each | self visitNode: each ] OrderedCollection>>do: OCASTSemanticAnalyzer>>visitSequenceNode: RBSequenceNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: OCASTSemanticAnalyzer>>visitMethodNode: RBMethodNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: OCASTSemanticAnalyzer>>analyze: RBMethodNode>>doSemanticAnalysis RBMethodNode>>doSemanticAnalysisInContext: [ ast doSemanticAnalysisInContext: self compilationContext ] in OpalCompiler>>doSemanticAnalysis in Block: [ ast doSemanticAnalysisInContext: self compilatio...etc... BlockClosure>>on:do: OpalCompiler>>doSemanticAnalysis [ ast := self parse. self doSemanticAnalysis ] in [ [ ast := self parse. self doSemanticAnalysis ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... BlockClosure>>on:do: [ [ ast := self parse. self doSemanticAnalysis ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ...Got startup errors: SyntaxErrorNotification: Cannot store into
Cheers Uko
Roassal 3D. Herâs the job: https://ci.inria.fr/moose/job/Roassal3d/ Uko On 01 Sep 2014, at 20:55, Nicolai Hess <nicolaihess@web.de> wrote:
which configuration are you trying to load?
2014-09-01 18:20 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk@me.com>: By the way, is there any way to check which is the problematic method? Because I failed to find it in log.
Uko
On 01 Sep 2014, at 17:45, Marcus Denker <marcus.denker@inria.fr> wrote:
On 01 Sep 2014, at 17:35, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
This this started at 29th and crashes image while loading configuration. Any idea whatâs wrong?
This means that you load code that assigns to arguments (method arguments). The new compiler allowed it (an oversight), the old one did notâ¦. now it is again not allowed.
(for bock arguments, it is still allowed).
==== Startup Error: SyntaxErrorNotification: Cannot store into OCSemanticError>>notify:at: OCSemanticError>>defaultAction [ :ex | ex defaultAction. ^ self compilationContext failBlock value ] in OpalCompiler>>doSemanticAnalysis in Block: [ :ex | ... BlockClosure>>cull: [ self exceptionHandlerBlock cull: exception ] in Context>>handleSignal: in Block: [ self exceptionHandlerBlock cull: exception ] BlockClosure>>ensure: Context>>handleSignal: OCSemanticError(Exception)>>signal OCASTSemanticAnalyzer>>storeIntoSpecialVariable: OCASTSemanticAnalyzer>>lookupVariableForWrite: OCASTSemanticAnalyzer>>visitAssignmentNode: RBAssignmentNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: [ :each | self visitNode: each ] in OCASTSemanticAnalyzer>>visitSequenceNode: in Block: [ :each | self visitNode: each ] OrderedCollection>>do: OCASTSemanticAnalyzer>>visitSequenceNode: RBSequenceNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: OCASTSemanticAnalyzer>>visitMethodNode: RBMethodNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: OCASTSemanticAnalyzer>>analyze: RBMethodNode>>doSemanticAnalysis RBMethodNode>>doSemanticAnalysisInContext: [ ast doSemanticAnalysisInContext: self compilationContext ] in OpalCompiler>>doSemanticAnalysis in Block: [ ast doSemanticAnalysisInContext: self compilatio...etc... BlockClosure>>on:do: OpalCompiler>>doSemanticAnalysis [ ast := self parse. self doSemanticAnalysis ] in [ [ ast := self parse. self doSemanticAnalysis ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... BlockClosure>>on:do: [ [ ast := self parse. self doSemanticAnalysis ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... Got startup errors: SyntaxErrorNotification: Cannot store into
Cheers Uko
R3IcoSphereShape>>addVertex: p found by loading an older build of R3 (#92 (Roassal3d.zip) Roassal3d.zip VERSION=stable PHARO=40) and changing the CriticRule RBFindBlockArgumentAssignment to search for methodArguments instead of block arguments and run the critic browser. But yes, the OC exception could be a bit more verbose :) nicolai 2014-09-01 21:06 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk@me.com>:
Roassal 3D. Herâs the job: https://ci.inria.fr/moose/job/Roassal3d/
Uko
On 01 Sep 2014, at 20:55, Nicolai Hess <nicolaihess@web.de> wrote:
which configuration are you trying to load?
2014-09-01 18:20 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk@me.com>:
By the way, is there any way to check which is the problematic method? Because I failed to find it in log.
Uko
On 01 Sep 2014, at 17:45, Marcus Denker <marcus.denker@inria.fr> wrote:
On 01 Sep 2014, at 17:35, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
This this started at 29th and crashes image while loading configuration. Any idea whatâs wrong?
This means that you load code that assigns to arguments (method arguments). The new compiler allowed it (an oversight), the old one did notâ¦. now it is again not allowed.
(for bock arguments, it is still allowed).
==== Startup Error: SyntaxErrorNotification: Cannot store intoOCSemanticError>>notify:at: OCSemanticError>>defaultAction [ :ex | ex defaultAction. ^ self compilationContext failBlock value ] in OpalCompiler>>doSemanticAnalysis in Block: [ :ex | ... BlockClosure>>cull: [ self exceptionHandlerBlock cull: exception ] in Context>>handleSignal: in Block: [ self exceptionHandlerBlock cull: exception ] BlockClosure>>ensure: Context>>handleSignal: OCSemanticError(Exception)>>signal OCASTSemanticAnalyzer>>storeIntoSpecialVariable: OCASTSemanticAnalyzer>>lookupVariableForWrite: OCASTSemanticAnalyzer>>visitAssignmentNode: RBAssignmentNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: [ :each | self visitNode: each ] in OCASTSemanticAnalyzer>>visitSequenceNode: in Block: [ :each | self visitNode: each ] OrderedCollection>>do: OCASTSemanticAnalyzer>>visitSequenceNode: RBSequenceNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: OCASTSemanticAnalyzer>>visitMethodNode: RBMethodNode>>acceptVisitor: OCASTSemanticAnalyzer(RBProgramNodeVisitor)>>visitNode: OCASTSemanticAnalyzer>>analyze: RBMethodNode>>doSemanticAnalysis RBMethodNode>>doSemanticAnalysisInContext: [ ast doSemanticAnalysisInContext: self compilationContext ] in OpalCompiler>>doSemanticAnalysis in Block: [ ast doSemanticAnalysisInContext: self compilatio...etc... BlockClosure>>on:do: OpalCompiler>>doSemanticAnalysis [ ast := self parse. self doSemanticAnalysis ] in [ [ ast := self parse. self doSemanticAnalysis ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ... BlockClosure>>on:do: [ [ ast := self parse. self doSemanticAnalysis ] on: OCSourceCodeChanged do: [ :notification | self source: notification newSourceCode. notification retry ]. cm := ast generate: self compilationContext compiledMethodTrailer ] in OpalCompiler>>compile in Block: [ ...Got startup errors: SyntaxErrorNotification: Cannot store into
Cheers Uko
Le 01/09/2014 22:04, Nicolai Hess a écrit :
R3IcoSphereShape>>addVertex: p
found by loading an older build of R3 (#92 (Roassal3d.zip) Roassal3d.zip VERSION=stable PHARO=40) and changing the CriticRule RBFindBlockArgumentAssignment to search for methodArguments instead of block arguments and run the critic browser.
I had a similar error yesterday trying to load Moose in a Pharo4 image in GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt: GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt: numbers |values| values := numbers collect: #first. "Lets check if the first and the last has different has different sign" ((values first * values last) negative and: [ (values includes: 0) not]) ifTrue: [ *** here is the problem *** Cannot store into -> numbers := self addZeroTo: numbers ]. (I didn't have time yet to find the moose mailing-list or group to report this bug) HTH regards Alain
You can find the Moose project mailing list coordinates here: http://www.moosetechnology.org/about/contact Doru On Tue, Sep 2, 2014 at 12:54 AM, Alain Rastoul <alr.dev@free.fr> wrote:
Le 01/09/2014 22:04, Nicolai Hess a écrit :
R3IcoSphereShape>>addVertex: p
found by loading an older build of R3 (#92 (Roassal3d.zip) Roassal3d.zip VERSION=stable PHARO=40) and changing the CriticRule RBFindBlockArgumentAssignment to search for methodArguments instead of block arguments and run the critic browser.
I had a similar error yesterday trying to load Moose in a Pharo4 image in GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt:
GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt: numbers |values| values := numbers collect: #first.
"Lets check if the first and the last has different has different sign" ((values first * values last) negative and: [ (values includes: 0) not]) ifTrue: [ *** here is the problem *** Cannot store into -> numbers := self addZeroTo: numbers ].
(I didn't have time yet to find the moose mailing-list or group to report this bug) HTH
regards
Alain
-- www.tudorgirba.com "Every thing has its own flow"
Moose is not supported yet for Pharo 4. We are still in the process of releasing it for Pharo 3 and we will move afterwards. If you want to play with it, it is more advisable to play in Pharo 3. Doru On Tue, Sep 2, 2014 at 6:49 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
You can find the Moose project mailing list coordinates here: http://www.moosetechnology.org/about/contact
Doru
On Tue, Sep 2, 2014 at 12:54 AM, Alain Rastoul <alr.dev@free.fr> wrote:
Le 01/09/2014 22:04, Nicolai Hess a écrit :
R3IcoSphereShape>>addVertex: p
found by loading an older build of R3 (#92 (Roassal3d.zip) Roassal3d.zip VERSION=stable PHARO=40) and changing the CriticRule RBFindBlockArgumentAssignment to search for methodArguments instead of block arguments and run the critic browser.
I had a similar error yesterday trying to load Moose in a Pharo4 image in GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt:
GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt: numbers |values| values := numbers collect: #first.
"Lets check if the first and the last has different has different sign" ((values first * values last) negative and: [ (values includes: 0) not]) ifTrue: [ *** here is the problem *** Cannot store into -> numbers := self addZeroTo: numbers ].
(I didn't have time yet to find the moose mailing-list or group to report this bug) HTH
regards
Alain
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com "Every thing has its own flow"
It i think just wonât load in Pharo4 because there is no configuration for PetitParser Uko On 02 Sep 2014, at 06:50, Tudor Girba <tudor@tudorgirba.com> wrote:
Moose is not supported yet for Pharo 4. We are still in the process of releasing it for Pharo 3 and we will move afterwards. If you want to play with it, it is more advisable to play in Pharo 3.
Doru
On Tue, Sep 2, 2014 at 6:49 AM, Tudor Girba <tudor@tudorgirba.com> wrote: You can find the Moose project mailing list coordinates here: http://www.moosetechnology.org/about/contact
Doru
On Tue, Sep 2, 2014 at 12:54 AM, Alain Rastoul <alr.dev@free.fr> wrote: Le 01/09/2014 22:04, Nicolai Hess a écrit :
R3IcoSphereShape>>addVertex: p
found by loading an older build of R3 (#92 (Roassal3d.zip) Roassal3d.zip VERSION=stable PHARO=40) and changing the CriticRule RBFindBlockArgumentAssignment to search for methodArguments instead of block arguments and run the critic browser.
I had a similar error yesterday trying to load Moose in a Pharo4 image in GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt:
GET2NumericLabelDecorator>>ifZeroIsMissingIncludeIt: numbers |values| values := numbers collect: #first.
"Lets check if the first and the last has different has different sign" ((values first * values last) negative and: [ (values includes: 0) not]) ifTrue: [ *** here is the problem *** Cannot store into -> numbers := self addZeroTo: numbers ].
(I didn't have time yet to find the moose mailing-list or group to report this bug) HTH
regards
Alain
-- www.tudorgirba.com
"Every thing has its own flow"
-- www.tudorgirba.com
"Every thing has its own flow"
Le 02/09/2014 06:50, Tudor Girba a écrit :
Moose is not supported yet for Pharo 4. We are still in the process of releasing it for Pharo 3 and we will move afterwards. If you want to play with it, it is more advisable to play in Pharo 3.
Doru
Thank you Doru, That's what I thought and that makes sense, however the error is still relevant to the new compiler, I thought it would help Uko. I registered to the moose mailing list but have problems with my email address since few days, don't know wtf is going on. Regards Alain
participants (5)
-
Alain Rastoul -
Marcus Denker -
Nicolai Hess -
Tudor Girba -
Yuriy Tymchuk