PharoCommandLineHandler
PharoCommandLineHandler is strange. What is real purpose of this class? Do we need it? It adds UsersManager dependency but I do not think that it really stops the processing of arguments. -- Pavel
which pharo version? On 2013-10-04, at 14:42, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
PharoCommandLineHandler is strange. What is real purpose of this class? Do we need it? It adds UsersManager dependency but I do not think that it really stops the processing of arguments.
-- Pavel
We introduced this class because of the Kernel jobs (see the class comment). So yes, it is essential for the Pharo Image, not for the Kernel (as you can see by its superclass). On 2013-10-04, at 14:46, Camillo Bruni <camillobruni@gmail.com> wrote:
which pharo version?
On 2013-10-04, at 14:42, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
PharoCommandLineHandler is strange. What is real purpose of this class? Do we need it? It adds UsersManager dependency but I do not think that it really stops the processing of arguments.
-- Pavel
It is not in the separate (or other) package so it still makes problems for Kernel jobs (I have to remove this class before shrinking). This information from the documentation does not seem to be valid: "It first checks if another handler is available. If so it will activate the found handler." -- Pavel 2013/10/4 Camillo Bruni <camillobruni@gmail.com>:
We introduced this class because of the Kernel jobs (see the class comment).
So yes, it is essential for the Pharo Image, not for the Kernel (as you can see by its superclass).
On 2013-10-04, at 14:46, Camillo Bruni <camillobruni@gmail.com> wrote:
which pharo version?
On 2013-10-04, at 14:42, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
PharoCommandLineHandler is strange. What is real purpose of this class? Do we need it? It adds UsersManager dependency but I do not think that it really stops the processing of arguments.
-- Pavel
On 2013-10-04, at 14:54, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
It is not in the separate (or other) package so it still makes problems for Kernel jobs (I have to remove this class before shrinking). This information from the documentation does not seem to be valid: "It first checks if another handler is available. If so it will activate the found handler."
Indeed, it is not fully correct: ./pharo Pharo.image eval '1+2' will activates the EvaluateCommandLineHandler (after going through the PharoCommandLineHandler), whereas ./pharo Pharo.image --help only activates the PharoCommandLineHandler. feel free to update the comments
participants (2)
-
Camillo Bruni -
Pavel Krivanek