LB Booster
« CommandLine$ oddity »

Welcome Guest. Please Login or Register.
Apr 1st, 2018, 04:24am



ATTENTION MEMBERS: Conforums will be closing it doors and discontinuing its service on April 15, 2018.
We apologize Conforums does not have any export functions to migrate data.
Ad-Free has been deactivated. Outstanding Ad-Free credits will be reimbursed to respective payment methods.

Thank you Conforums members.
Speed up Liberty BASIC programs by up to ten times!
Compile Liberty BASIC programs to compact, standalone executables!
Overcome many of Liberty BASIC's bugs and limitations!
LB Booster Resources
LB Booster documentation
LB Booster Home Page
LB Booster technical Wiki
Just BASIC forum
BBC BASIC Home Page
Liberty BASIC forum (the original)

« Previous Topic | Next Topic »
Pages: 1  Notify Send Topic Print
 thread  Author  Topic: CommandLine$ oddity  (Read 697 times)
RobM
Junior Member
ImageImage


member is offline

Avatar




PM


Posts: 91
xx Re: CommandLine$ oddity
« Reply #3 on: Dec 11th, 2014, 6:21pm »

So LB must be using GetCommandLine but that does really explain why there would be a difference.

Either way, this is probably something that is done behind the scenes in Smalltalk and Carl wouldn't be able to fix it.
User IP Logged

Richard Russell
Administrator
ImageImageImageImageImage


member is offline

Avatar




Homepage PM


Posts: 1348
xx Re: CommandLine$ oddity
« Reply #4 on: Dec 11th, 2014, 9:36pm »

on Dec 11th, 2014, 6:21pm, RobM wrote:
Either way, this is probably something that is done behind the scenes in Smalltalk and Carl wouldn't be able to fix it.

I see there's currently a thread at the LB Community Forum which indicates that the problems with CommandLine$ go far deeper than I realised. Even when consistently run from a command prompt the contents of the variable depend on things like whether you enclose the program name in quotes or not!

If the issue is a fault in Smalltalk Carl should be able to workaround it by calling the GetCommandLine API himself (thereby bypassing Smalltalk's command line processing) and parsing it to return the wanted command 'tail' - which basically involves removing the initial (possibly quoted) path/filename of the executable.

Richard.
User IP Logged

Pages: 1  Notify Send Topic Print
« Previous Topic | Next Topic »

| |

This forum powered for FREE by Conforums ©
Terms of Service | Privacy Policy | Conforums Support | Parental Controls