> El 16-06-2017, a las 10:34, Holger Freyther <hol...@freyther.de> escribió:
>
>
>> On 12. Jun 2017, at 16:41, Juraj Kubelka <juraj.kube...@icloud.com> wrote:
>>
>> Hi Holger,
>>
>> I have an impression that it can be solved by using
>> "--no-default-preferences” option:
>> ./pharo Pharo.image --no-default-preferences
>>
>> Is it a good solution for you? Or do you need to load some preferences?
>
> Right, unsetting HOME and then using --no-default-preferences makes the error
> go away.
>
>
>
>> Another option could be implementing an error signal, e.g.,
>> CantFindOriginError in the cantFindOriginError method and catch this in the
>> GlobalIdentifier object.
>
> I wonder if "FileLocator home exists" should really throw an exception in
> case {home} can not be resolved.
>
> a.) Just because it can not be resolved, it might still exist?
> b.) If it can not be resolved it doesn't exist from an image point of view?
I think it is better to throw an exception. Then someone is sure that does not
use a code, that needs {home} directory, but cannot.
Maybe there could be a specialized error class for this. Now it uses Error, if
I remember well.
Juraj
>
> holger
