[Pharo-project] loading code from command line inovcation

Igor Stasenko siguctua at gmail.com
Fri Jun 3 19:04:17 EDT 2011


On 31 May 2011 13:50, Stefan Marr <pharo at stefan-marr.de> wrote:
> Hi Igor:
>
> On 31 May 2011, at 11:17, Igor Stasenko wrote:
>
>> Any error on startup will lead to writing error to log and quitting to OS.
>> Since scripts are processed during startup, error in script leads to
>> quitting to OS.
>> To what i see, everything works as expected:
>> on error during startup, an image leaves to the system.
>>
>> Maybe we should change a script manager to process script only after
>> full startup is done.
>> So, then instead of quitting from image you will have a debugger open.
>
> Another detail is, that users on the commandline expect errors to go to stderr and not to some 'hidden' log file.
>

yeah yeah. the problem is that no all VMs support this by default.
So it will be even worse if image will rely on non-existing features in VM.

> Would it be possible to have that recognized on startup and have errors redirected to stderr instead of a log file?
>

Sure. Changing few lines of code could do it.
See SmalltalkImage>>openLog

> Thanks
> Stefan
>


-- 
Best regards,
Igor Stasenko AKA sig.




More information about the Pharo-dev mailing list