Nicolai Hess wrote:
Thanks Nicolas. So given that its similar across platforms and reflects the system-level semantics, probably we should not change its behaviour, and handle this case at the PharoLauncher level. However it would be useful in Image to get something like an 'InvalidCrossVolume' exception. I'm not sure off-hand how to approach that. cheers -ben
|
- Re: [Pharo-dev] PharoLauncher on Windows not the latest vers... kilon alios
- Re: [Pharo-dev] PharoLauncher on Windows not the latest vers... Ben Coman
- Re: [Pharo-dev] PharoLauncher on Windows not the latest vers... kilon alios
- Re: [Pharo-dev] PharoLauncher on Windows not the latest vers... Tim Mackinnon
- Re: [Pharo-dev] PharoLauncher on Windows not the latest vers... kilon alios
- Re: [Pharo-dev] PharoLauncher on Windows not the latest vers... kilon alios
- Re: [Pharo-dev] PharoLauncher on Windows not the latest vers... Tim Mackinnon
- Re: [Pharo-dev] PharoLauncher on Windows not the latest vers... kilon alios
- Re: [Pharo-dev] PharoLauncher on Windows not the latest vers... kilon alios
- Re: [Pharo-dev] PharoLauncher on Windows not the latest vers... Tim Mackinnon
- Re: [Pharo-dev] [Vm-dev] Re: PharoLauncher on Windows not th... btc
- Re: [Pharo-dev] [Vm-dev] Re: PharoLauncher on Windows not th... Ben Coman
- Re: [Pharo-dev] [Vm-dev] Re: PharoLauncher on Windows not th... Nicolai Hess