What a mess

I trying to figure out how command-line arguments are passed to image...
and this is complete mess.

I cannot determine why on Windoze, a script argument passed in command
line is ignored.

--
Best regards,
Igor Stasenko AKA sig.

> I trying to figure out how command-line arguments are passed to image...
> and this is complete mess.

what if this is broken don't fix it....
;D

Yes we will fix that tooooooooooo

>
> I cannot determine why on Windoze, a script argument passed in command
> line is ignored.
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>

Apparently, it is not broken at all. Like Torsten said, you have to explicitly mention that you want the "file:" if you want to specify an absolute path.

Cheers,
Doru


On 16 Mar 2011, at 16:14, Stéphane Ducasse wrote:

--
www.tudorgirba.com

"Presenting is storytelling."

What igor means is that it would be good to have a consistent and unified way to pass information to the vm.
Right now the mac vm does not handle well -headless and each vm has its different ways to handle arguments.

Stef

On Mar 16, 2011, at 4:23 PM, Tudor Girba wrote:

yes... we need a common command line options (and maybe very specific platform command line options too, but there should be a common way to do common things :)

best,
Esteban

El 16/03/2011, a las 12:38p.m., Stéphane Ducasse escribió:

+ 1

> yes... we need a common command line options (and maybe very specific platform command line options too, but there should be a common way to do common things :)
>
> best,
> Esteban

On 16 March 2011 16:23, Tudor Girba <[hidden email]> wrote:
> Apparently, it is not broken at all. Like Torsten said, you have to explicitly mention that you want the "file:" if you want to specify an absolute path.
>

Its not broken.. But as to me it contains too many hops between the
initial receiver of #startUp message
and the code, which actually decides what to do and how to do.

Its not worked because i had a mistake in script. And it was silently
ignored the script, instead of raising error or notifying me or
something like that...
I don't like when system is too clever and try to do magic under the hood..
It would be much better to use explicit protocol for communicating
with image, so if something goes wrong, you know exactly where.

And currently if you run VM from command line with following:

<VM> myImage.image -foo bar -baz

there is no way to tell what will happen.
it could tread '-foo' as a file and try to read from it,
or other VMs could treat it as a command line option and hide it from
language side completely (so you cannot see it at all)...

as i said.. it is too clever :)

> Cheers,
> Doru
>
>
> On 16 Mar 2011, at 16:14, Stéphane Ducasse wrote:
>

--
Best regards,
Igor Stasenko AKA sig.

+1

Em 16-03-2011 12:42, Esteban Lorenzano escreveu:
> yes... we need a common command line options (and maybe very specific platform command line options too, but there should be a common way to do common things :)
>
> best,
> Esteban