|
|
Re: [Acceleo] Problem of type with empty collections [message #1795885 is a reply to message #1795878] |
Mon, 01 October 2018 23:28 |
Mad Vin Messages: 40 Registered: September 2013 |
Member |
|
|
OMG ! Seriously ?!
I can't understand where is the ambiguity when you write :
It is clearly written that this empty Set shall receive String typed elements only, so there is no reason to be interpreted as a Set(OclVoid).
I've just read the last specifications of OCL (version 2.4), and the syntax :
<collectionKind>(<collectionType>){}
is not a valid one, the part "(<collectionType)" is not allowed according to these specifications, but is allowed by Acceleo however.
So is this just a syntax accepted by Acceleo only and having no effect with OCL, or the used implementation of OCL allows this too but ignore it ?
It's really a shame... This lack is totally incomprehensible. -_-°
So I keep my workaround by using the filter operation... I won't have better... :/
And logically, I suppose :
should be a workaround too...
Regards.
[Updated on: Mon, 01 October 2018 23:39] Report message to a moderator
|
|
|
|
Powered by
FUDForum. Page generated in 0.04534 seconds