On Tue, Nov 29, 2011 at 11:54 PM, Alexander Lazarevi�� <laza@blobworks.com> wrote:

2011/11/29 Eliot Miranda <eliot.miranda@gmail.com>

�� -1 => executable name
�� -2 .. -n => VM arguments *including* image (if explicitly supplied).

Before we had (at least on Linux and I guess with the StackVM):

�� 0 => executable name
�� -1 .. -n => VM arguments *including* image (if explicitly supplied).

Right. ��And that makes sense.

��

Why the need to change that? And what's 0 returning now? The same as 1 (with path)?

I wanted all three platforms to be the same (the Mac was not answering any VM parameters at all, and Windows was returning the executable in -1). ��But I missed that 0 was answering the executable name. ��It makes no sense for Smalltalk getSystemAttribute: 0 and Smalltalk getSystemAttribute: -1 to answer the same thing. ��I will change it (back) to

�� 0 => executable name

�� -1 .. -n => VM arguments *including* image (if explicitly supplied).

and do so on all platforms.

Thanks for spotting this.

Alex

��