On 07 Apr 2014, at 14:02, Sergi Reyner wrote:
> 2014-04-07 11:51 GMT+01:00 Marcus Denker :
> In 4.0, we will remove the old compiler and then we can see how to make the
> API perfect.
>
> Will it be able to decompile by then?
>
Yes, we will solve that problem, too.
Marcus
Thanks guys!
On Apr 7, 2014 4:36 PM, "Camille Teruel" wrote:
>
> On 7 avr. 2014, at 16:31, Clément Bera wrote:
>
> Hello,
>
> I do not like 'Smalltalk evaluate:' either.
>
> One solution is to do 'self class compiler evaluate:'.
>
>
> Yes IMO, calling #compiler on a class is the best solution si
On 7 avr. 2014, at 16:31, Clément Bera wrote:
> Hello,
>
> I do not like 'Smalltalk evaluate:' either.
>
> One solution is to do 'self class compiler evaluate:'.
Yes IMO, calling #compiler on a class is the best solution since it returns a
compiler with the options that the class defines.
Hello,
I do not like 'Smalltalk evaluate:' either.
One solution is to do 'self class compiler evaluate:'.
2014-04-07 5:02 GMT-07:00 Sergi Reyner :
> 2014-04-07 11:51 GMT+01:00 Marcus Denker :
>
> In 4.0, we will remove the old compiler and then we can see how to make
>> the API perfect.
>>
>
>
2014-04-07 11:51 GMT+01:00 Marcus Denker :
> In 4.0, we will remove the old compiler and then we can see how to make
> the API perfect.
>
Will it be able to decompile by then?
Cheers,
Sergi
On 07 Apr 2014, at 12:15, Andre Hora wrote:
> Hello,
>
> Recently in Pharo there was some tendency to replace Compiler evaluate: by
> Smalltalk evaluate:.
> Stef does not seem to agree with that.
> My question is which one is the correct convention to call #evaluate: ?
>
The problem is that
Hello,
Recently in Pharo there was some tendency to replace Compiler evaluate: by
Smalltalk evaluate:.
Stef does not seem to agree with that.
My question is which one is the correct convention to call #evaluate: ?
thanks in advance,
--
Andre Hora
