Hi Jeff,
On Mon, Feb 16, 2015 at 9:06 AM, J.F. Rick <[email protected]> wrote:
> It's probably obvious to you now but arguments up to and including the
>> image name are processed by the VM and arguments thereafter are left for
>> the image.
>
>
> Indeed. I've just always been used to practice of setting flags first when
> executing a unix command. Perhaps this would be worthwhile adding as a note
> in the documentation that spits out.
>
+1. Note that the VM itself does this. Heres what the Mac VM spits out
when given the -help flag:
McStalker.oscogvm$
./build.macos32x86/squeak.stack.spur/Fast.app/Contents/MacOS/Squeak -help
Usage: ./build.macos32x86/squeak.stack.spur/Fast.app/Contents/MacOS/Squeak
[<option>...] [<imageName> [<argument>...]]
./build.macos32x86/squeak.stack.spur/Fast.app/Contents/MacOS/Squeak
[<option>...] -- [<argument>...]
Common <option>s:
-help print this help message, then exit
-memory <size>[mk] use fixed heap size (added to image size)
...
Based on that feedback, I tried "./pharo --headless --no-quit
> ./Pharo.image" pretty quickly. It didn't occur to me then that order might
> make a difference as one set of tags is for the VM and the other is for the
> scripting ability. Now that I better understand it, it makes sense. But a
> note of warning there would have been helpful. It seems we've come a long
> way from the early days of the Squeak VM.
>
> Cheers,
>
> Jeff
>
> --
> Jochen "Jeff" Rick, Ph.D.
> http://www.je77.com/
> Skype ID: jochenrick
>
--
best,
Eliot
