The problem with command-line arguments as a file names, like: cat myfile.foo is that the location of myfile.foo is determined by using a search path , usually provided in environment PATH var of a shell. I worked in a different unix shells, and some of them, do not adding/using the ./ into the search path by default, which means that cat myfile.foo will end up with 'file not found' message, while cat ./myfile.foo will work fine. i think that squeak should follow the shell semantics and do not try to automatically expand the pure file name, like foo.bar into something like: ./foo.bar, or ~/foo.bar 2009/9/2 John M McIntosh <johnmci@smalltalkconsulting.com>:
I think  here you are trying to get to test.sq
I only adjust the incoming image name in the VM looking for ~ for example, and resolving usage of ./ and ../
The additional command line items are then passed to the image unchanged, so it sees only 'test.sq' Â as the path name. You would have to check the smalltalk code at the point where it gets the command line parm and decide if it's 'test.sq' should that really be './test.sq' You might also try putting './test.sq' on the command line and see if that works.
On 2-Sep-09, at 9:23 AM, Stéphane Ducasse wrote:
The full path requirement should be considered a bug from my perspective.
mine too and I thought that john fixed that. So did you try without?
-- = = = ======================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Â Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. Â http://www.smalltalkconsulting.com = = = ========================================================================
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.