>
> I can.
>
> I'll try to make sure I test it with a larger set of tests next, but, so far,
> the only change I had to do was that doSilently: thing.
>
> Now, would anyone has a nice configuration showing how to customize for Pharo
> 2.0/Pharo 1.4 ?
The idea is that you have your baseline and version
then you add symbolic version
stable: spec
<symbolicVersion: #'stable'>
spec for: #'common' version: '1.1'.
spec for: #'pharo1.4.x' version: '1.4'
spec for: #'pharo2.0.x' version: '1.8'
Have a look at the metacello chapter
>>> and I'm looking for the equivalent to
>>> SystemChangeNotifier>>__doSilently:. Is it
>>> SystemAnnouncer>>__suspendAllWhile:?
>>>
>>> (doSilently: is used in SmaCC tests).
>>>
>>>
>>> There is also a nice #valueWithoutNotifications in BlockClosure.
>>>
>>> BTW, does it make sense to port SmaCC?
>>
>> faster
>> more compact
>>> Which use case do you have in which you prefer SmaCC over say PetitParse?
>>> I took a look few weeks ago to something done in SmaCC and it was full
>>> of ugly unmaintainable class side tables…..
>>
>> you do not have to read the assembly code of your Smalltalk programs. :)
>>
>> Smacc represents the traditional way to build parser and it is important
>> to also have it around and kicking.
>
> It could be nice to upgrade Pharo's SmaCC to the GLR parsing which exists in
> SmaCC for VW and Dolphin.
Yes!
Definitively.
Stef
