Issue 5176 in pharo: commandline scripts should output to stderr

Status: Accepted
Owner: [hidden email]

New issue 5176 by [hidden email]: commandline scripts should output  
to stderr
http://code.google.com/p/pharo/issues/detail?id=5176

when a commandline script fails to load it should output an error message  
on stderr.
otherwise there is not real feedback if the image is run in normal, visual  
mode.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #1 on issue 5176 by [hidden email]: commandline scripts  
should output to stderr
http://code.google.com/p/pharo/issues/detail?id=5176

Yes they should !

But a PharoDebug file should still be written in most circumstances.

See also NonInteractiveTranscript.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #2 on issue 5176 by [hidden email]: commandline scripts  
should output to stderr
http://code.google.com/p/pharo/issues/detail?id=5176

I did a first version which outputs the following:


file:///Users/cami-data/education/phd/project/pharo/scriptCompilerWarning/script.st
Syntax Error on line 1: 'Nothing more expected'
===============================================
01: kjhgjkghghjk l '[[pp[\'[; ]][][][]A
               ^
02: asdf
03:
04: asd
05: f
06: asdfasdfasdf
07: asdf
08: asdfasdfasd
09: asdfg
10:
11: sadf
12:

do we need anything else?


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #3 on issue 5176 by [hidden email]: commandline scripts  
should output to stderr
http://code.google.com/p/pharo/issues/detail?id=5176

Did you see

http://code.google.com/p/pharo/issues/detail?id=5227

I think these are related.

The output in your example is quite cool, better I guess.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #4 on issue 5176 by [hidden email]: commandline scripts  
should output to stderr
http://code.google.com/p/pharo/issues/detail?id=5176

Another related question that I recently asked:

http://forum.world.st/End-of-startup-script-behavior-td4343987.html

What method deals with the startup script loading ? So that I can have a  
look myself.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #5 on issue 5176 by [hidden email]: commandline scripts  
should output to stderr
http://code.google.com/p/pharo/issues/detail?id=5176

most of it is in CodeLoader


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: Duplicate
        Mergedinto: 5227

Comment #6 on issue 5176 by [hidden email]: commandline scripts  
should output to stderr
http://code.google.com/p/pharo/issues/detail?id=5176

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker