|
|
|
Re: Hexcode terminal vs Named Colors terminal. Terminal structuring problem. [message #1699441 is a reply to message #1699413] |
Wed, 24 June 2015 11:11 |
Hallvard Traetteberg Messages: 673 Registered: July 2009 Location: Trondheim, Norway |
Senior Member |
|
|
Perhaps you should include the # as part of the terminal, or else a
Hexcode may start grabbing other input?
Hallvard
On 24.06.15 09:46, Anton Bergman wrote:
> In my language, I want to be able to describe a color both as a name,
> and as a Hexcode. For example:
>
> I have both terminal COLOR: 'AliceBlue'|'Aqua'|'Beige'|'Coral' ...
> and so on, as well as
>
> terminal HEXCODE: ('A' .. 'F' | '0' .. '9') ('A' .. 'F' | '0' .. '9')
> ('A' .. 'F' | '0' .. '9') ('A' .. 'F' | '0' .. '9') ('A' .. 'F' | '0' ..
> '9') ('A' .. 'F' | '0' .. '9').
>
> These are going to be used to put a color on a participant in a diagram.
> For example, i want to be able to write both
> Participant Bob #F912AAA as well as Participant Bob #Beige in my DSL.
>
> How would I go about structuring this? I have tried to do something like
> this in the participant rule:
> Participant: 'Participant' ID '#' (COLOR|HEXCODE) ;
>
> but it throws me a lot of errors with Decision can match input such as
> "NumberSign OliveDrab" using multiple alternatives: 1, 2
> As a result, alternative(s) 2 were disabled for that input
>
> Can anyone help me?
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05148 seconds