Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Modeling » ATL » no viable alternative at input...
no viable alternative at input... [message #1808516] Wed, 26 June 2019 08:12 Go to next message
Marshall Charron is currently offline Marshall CharronFriend
Messages: 72
Registered: August 2018
Member
I wrote this rule in ATL :

rule NewPerson (na: String, s_na: String) {
	to
		p : Objet!Feature (
			name <-  'nok'
		)
	do {
		 p.name <- 'ok'
	}
}


But I am getting this syntax error for the 'do {}' block :

no viable alternative at input 'name'


It is really bizarre because everything seems correct.

What could a possible cause of this ?

Thank you

[Updated on: Wed, 26 June 2019 08:26]

Report message to a moderator

Re: no viable alternative at input... [message #1808606 is a reply to message #1808516] Thu, 27 June 2019 17:17 Go to previous messageGo to next message
Dennis Wagelaar is currently offline Dennis WagelaarFriend
Messages: 589
Registered: September 2012
Location: Belgium
Senior Member

"do" blocks contain imperative statements, which must end with a ';'.

Cheers,
Dennis
Re: no viable alternative at input... [message #1808649 is a reply to message #1808606] Fri, 28 June 2019 08:08 Go to previous message
Marshall Charron is currently offline Marshall CharronFriend
Messages: 72
Registered: August 2018
Member
Thanks
Previous Topic:how to get xmi:type of UML in atl rule
Next Topic:Add an element to a sequence
Goto Forum:
  


Current Time: Wed Apr 24 22:00:46 GMT 2024

Powered by FUDForum. Page generated in 0.03029 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top