What about trying

    Metacello new
    baseline: 'SmaCC';
    repository: 'github://ThierryGoubier/SmaCC';
    load

This worked in Pharo 6.1 in November 2017

On 10/16/18, Dimitris Chloupis <kilon.al...@gmail.com> wrote:
> thanks for the info Peter , will give it a try :)
>
> On Tue, Oct 16, 2018 at 7:35 PM PBKResearch <pe...@pbkresearch.co.uk>
> wrote:
>
>> Dimitris
>>
>>
>>
>> If you download the latest Moose Suite 6.1, you will have Pharo 6.1 with
>> lots of extra packages, including SmaCC. The SmaCC includes compilers for
>> C, Smalltalk and Java, among others, but with little or no documentation.
>> I
>> am not a SmaCC expert, so I can’t say whether it will do what you want,
>> but
>> at least it will give you a start. Moose also includes PetitParser and
>> PP2,if you want to try other parsing approaches. Of course, the Windows
>> version is 32-bit only, for reasons explained elsewhere in this thread.
>>
>>
>>
>> HTH
>>
>>
>>
>> Peter Kenny
>>
>>
>>
>> *From:* Pharo-users <pharo-users-boun...@lists.pharo.org> *On Behalf Of
>> *Dimitris
>> Chloupis
>> *Sent:* 16 October 2018 15:40
>> *To:* Any question about pharo is welcome <pharo-users@lists.pharo.org>
>> *Subject:* [Pharo-users] Installing SmaCC
>>
>>
>>
>> Hey guys
>>
>>
>>
>> I downloaded the latest Pharo 6.1 64bit for Windows and tried to install
>> SmaCC through the catalog browser but it failed
>>
>>
>>
>> I did manage to install it following the instruction in the github repo
>> but I see that I am missing most parser packages.
>>
>>
>>
>> The languages I am interested are Smalltalk (which is included) and C (if
>> possible C++ too) cause I will be creating a new language which will be a
>> cross between C and Smalltalk (very similar to smalltalk syntax but with
>> the addtion of C types and no GC and dynamic typing and also a partial
>> implementation of OOP that is quite diffirent). My goal is compilation of
>> my language to readable C code so the ability to parse also existing C
>> code
>> is needed.
>>
>>
>>
>> Any help is greatly appreciated , thanks :)
>>
>

Reply via email to