nice , good to know that is already a feature in another smalltalk
implementation. I decided finally to go against the idea of new sytax or
the heavy usage of Array symbols. Instead I will be using standard 100%
Pharo syntax. Fortunately Smalltalk syntax is so minimal that allows me to
do this with
On Wed, Oct 17, 2018 at 01:38:36PM +0300, Dimitris Chloupis wrote:
> About your last part on platforms, I will be providing a way to inline C
> code so one can you use C macros to detect the platform and generate code
> accordingly.
Smalltalk/X allows inline C. Not sure about macros though, as I
>> 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
>>>
no I wont be introducing new syntax, I rather keep this 100% smalltalk.Also
LowTalk uses GC which is a no go for me.
this is the "syntax" I am considering so its fully compatible with Pharo
--
SomeClass >> helloWorld: aMessage
#(char* aMessage newMessage
Perhaps a C-syntax front-end for Lowtalk would be interesting?
http://forum.world.st/Re-ANN-Lowtalk-a-new-Smalltalk-dialect-that-could-eventually-replace-Slang-td4966907.html
cheers -ben
On Wed, 17 Oct 2018 at 19:37, Dimitris Chloupis
wrote:
> there will be no remap of variable names, this is a
there will be no remap of variable names, this is a strict compiler if you
can even call it a compiler. Your variable names will stay exactly the same
in the C side , a concern here was that Pharo would not allow to have names
like "my_personal_function". All the praise to Pharo it actually allows
Le mer. 17 oct. 2018 à 12:39, Dimitris Chloupis
a écrit :
>
> About your last part on platforms, I will be providing a way to inline C code
> so one can you use C macros to detect the platform and generate code
> accordingly. Or this could happen via a pragma too, it should not be an
> issue. T
About your last part on platforms, I will be providing a way to inline C
code so one can you use C macros to detect the platform and generate code
accordingly. Or this could happen via a pragma too, it should not be an
issue. This also a reason why I previously talked about an "in place"
annotation
Hello Allistair
I have used Slang only once and it was generating code that was indeed
readbale but my aim is for more finer control over the output. Lets say I
want import a specific C header file or I want a string to map to custom C
type I created etc. So yes Slang is by no mean a bad tool at a
Hi Dimitris,
As someone currently learning to use Slang (i.e. not an expert), I've
added my 2c below...
On Wed, 17 Oct 2018 at 11:06, Dimitris Chloupis wrote:
>
> Thierry you have done it !!! you just gave a very easy solution to my
> problems.
>
> Yeap Slang is quite close to what I am thinkin
What about trying
> >> >>> > >
> >> >>> > >
> >> >>> > > Metacello new
> >> >>> > > baseline: 'SmaCC';
> >> >>> > > repository: 'github://Thier
pository: 'github://ThierryGoubier/SmaCC';
>> >>> > > load
>> >>> > >
>> >>> > > This worked in Pharo 6.1 in November 2017
>> >>> > >
>> &
;> > <mailto: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
> >>> > mailto:pe.
>>> > >>>
>>> > >>>
>>> > >>>
>>> > >>> If you download the latest Moose Suite 6.1, you will have
>>> > Pharo
>>> > 6.1 with
>>> > >>> lots
>> 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
; >>> 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
dows
>>> version is 32-bit only, for reasons explained elsewhere in this
thread.
>>>
>>>
>>>
>>> HTH
>>>
>>>
>>>
>>> Peter Kenny
>>>
>>>
>>>
gt; 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 Win
re in this thread.
>>>
>>>
>>>
>>> HTH
>>>
>>>
>>>
>>> Peter Kenny
>>>
>>>
>>>
>>> *From:* Pharo-users *On Behalf Of
>>> *Dimitris
>>> Chloupis
>>> *Sent:* 16 October 2018
rse, the Windows
>> version is 32-bit only, for reasons explained elsewhere in this thread.
>>
>>
>>
>> HTH
>>
>>
>>
>> Peter Kenny
>>
>>
>>
>> *From:* Pharo-users *On Behalf Of
>> *Dimitris
>> Chloupis
>> *S
he Windows
> version is 32-bit only, for reasons explained elsewhere in this thread.
>
>
>
> HTH
>
>
>
> Peter Kenny
>
>
>
> *From:* Pharo-users *On Behalf Of
> *Dimitris
> Chloupis
> *Sent:* 16 October 2018 15:40
> *To:* Any question about pharo i
Dimitris
Chloupis
Sent: 16 October 2018 15:40
To: Any question about pharo is welcome
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
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
23 matches
Mail list logo
