I’m puzzled. I have the same rules in two grammars one parse a sequence and
the other not.
self parse: ‘payable internal'
_FunctionTypeNameOptions
:
| FunctionTypeNameOptions
;
FunctionTypeNameOptions
: FunctionTypeNameOption 'option' {{}}
| FunctionTypeNameOptions FunctionTypeNameOption 'option'
I’m puzzled. I have the same rules in two grammars one parse a sequence and
the other not.
self parse: ‘payable internal'
_FunctionTypeNameOptions
:
| FunctionTypeNameOptions
;
FunctionTypeNameOptions
: FunctionTypeNameOption 'option' {{}}
| FunctionTypeNameOptions FunctionTypeNameOption
Le 27/03/2017 à 21:12, Stephane Ducasse a écrit :
what was strange is that this version
: \s+;
%root MultiListObject;
%prefix XPML;
modifiers_opt
:
| modifiers
;
modifiers
: modifier 'modifier' {{}}
| modifiers modifier 'modifier' {{}}
;
modifier
: "public" 'token' {{Modifier}}
| "protected" '
what was strange is that this version
: \s+;
%root MultiListObject;
%prefix XPML;
modifiers_opt
:
| modifiers
;
modifiers
: modifier 'modifier' {{}}
| modifiers modifier 'modifier' {{}}
;
modifier
: "public" 'token' {{Modifier}}
| "protected" 'token' {{Modifier}}
| "private" 'token' {{Modifier}}
Hi Stéphane,
can you send the complete grammar? The %root directive should have no
impact on parse failures.
Thierry
Le 27/03/2017 à 18:40, Stephane Ducasse a écrit :
Apparently there is an interaction with the root directives.
On Mon, Mar 27, 2017 at 6:34 PM, Stephane Ducasse
mailto:stepha
Apparently there is an interaction with the root directives.
On Mon, Mar 27, 2017 at 6:34 PM, Stephane Ducasse
wrote:
> Now I tried to hook modifier logic to test and I cannot have two modifiers.
> I thought that
>
> modifiers
> : modifier 'modifier'
> | modifiers modifier 'modifier'
> ;
> allow
Now I tried to hook modifier logic to test and I cannot have two modifiers.
I thought that
modifiers
: modifier 'modifier'
| modifiers modifier 'modifier'
;
allows one to have 'public static' but apparently not so I'm totally
confused.
On Mon, Mar 27, 2017 at 6:30 PM, Stephane Ducasse
wrote:
>
Hi john
I'm learning smacc as a challenge :) I read a review the tutorial that we
extracted form your doc.
I have the following expression
FunctionTypeName = 'function' TypeNameList ( 'internal' | 'external' |
'constant' | 'payable' )* ( 'returns' TypeNameList )?
and I started to handle the 'in
They come with the ConfigurationOfSmaCC which is already in the Moose image.
Doru
> On Mar 27, 2017, at 4:52 PM, Stephane Ducasse wrote:
>
> Hi
>
> where can I load the Smacc gt extension and debugger extensions?
>
> Stef
--
www.tudorgirba.com
www.feenk.com
"Speaking louder won't make the
Hi
where can I load the Smacc gt extension and debugger extensions?
Stef
Hi guys
Tomcat is looking for Smalltalkers in Germany.
Contact them not me :)
richard.v-lava...@tomcat.de
christian.m...@tomcat.de
Stef
Actually now we are still looking for more Smalltalker again.
Therefore today I turn to You and want to ask, it You know anybody, who has
at least 2-3 Y
On Mon, Mar 27, 2017 at 1:01 PM, Guillermo Polito wrote:
>
>
> On Mon, Mar 27, 2017 at 12:04 PM, Denis Kudriashov
> wrote:
>
>>
>> 2017-03-27 11:34 GMT+02:00 Guillermo Polito :
>>
>>> Well, you can capture the signal, but the problem is not the signal
>>> itself but what caused the problem. The
On Mon, Mar 27, 2017 at 12:04 PM, Denis Kudriashov
wrote:
>
> 2017-03-27 11:34 GMT+02:00 Guillermo Polito :
>
>> Well, you can capture the signal, but the problem is not the signal
>> itself but what caused the problem. The most common case of segfaut is
>> memory corruption (and thus a program t
Hi Sven,
i completely agree my monday is not necessarily your monday, but my
monday is my monday independently of when i initiate it. my monday (a
few days ago) does _not begin at another utc because of a dst change in
the meantime. this behaviour could result in additional problems, apart
fr
2017-03-27 11:34 GMT+02:00 Guillermo Polito :
> Well, you can capture the signal, but the problem is not the signal itself
> but what caused the problem. The most common case of segfaut is memory
> corruption (and thus a program that tries to wrongly interpret wrong
> addresses). If you already co
On Sun, Mar 26, 2017 at 7:21 PM, Peter Uhnak wrote:
> On Sun, Mar 26, 2017 at 05:45:04PM +0200, Esteban Lorenzano wrote:
> >
> > > On 26 Mar 2017, at 15:40, Peter Uhnak wrote:
> > >
> > > Hi,
> > >
> > > is it possible to use UFFI and avoid crashing the image when the
> called code segfaults?
>
Thanks for the tip but I know that. I have full access to the voyage code.
Without knowing the reason and context an issue is useless.
Norbert
> Am 26.03.2017 um 19:35 schrieb Stephane Ducasse :
>
> Add an issue in the Voyage github repo and do a pull request to push esteban
> releasing a new
17 matches
Mail list logo