Hi,
In Pharo3 we had the bug that assigning to method arguments was allowed.
*Block* arguments are traditionally assignable, but this is equally a bad idea
(there was already a setting
to forbid it, but no idea how to make it a default without making a lot of code
unlovable).
First we made met
This sounds like a good strategy this difference between interactive and
loading time.
On 7/10/14 18:25, Marcus Denker wrote:
Hi,
In Pharo3 we had the bug that assigning to method arguments was allowed.
*Block* arguments are traditionally assignable, but this is equally a bad idea
(there was
Indeed, I like this approach. Nicely done.
Doru
On Tue, Oct 7, 2014 at 9:11 PM, stepharo wrote:
> This sounds like a good strategy this difference between interactive and
> loading time.
>
>
> On 7/10/14 18:25, Marcus Denker wrote:
>
>> Hi,
>>
>> In Pharo3 we had the bug that assigning to metho
If I evaluate: (CodeImporter evaluateFileNamed: 'foo.st')
In a headless pharo image, does it count as interactive?
Regards!
Esteban A. Maringolo
2014-10-07 16:31 GMT-03:00 Tudor Girba :
> Indeed, I like this approach. Nicely done.
>
> Doru
>
> On Tue, Oct 7, 2014 at 9:11 PM, stepharo wrote:
>
> On 07 Oct 2014, at 21:42, Esteban A. Maringolo wrote:
>
> If I evaluate: (CodeImporter evaluateFileNamed: 'foo.st')
>
> In a headless pharo image, does it count as interactive?
>
Normally not… it should be non-interactive in all cases. (like loading
monticello, loading change sets…)
