Welcome Guest. Please Login or Register. Apr 1st, 2018, 03:46am
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!
Carl has also released announced Liberty BASIC v4.5 - . Does that affect the current version of LB Booster in any way?
Further to my earlier comments I've just noticed that Carl has done something superficially strange. In the 'Liberty BASIC v4.5 beta 1 release notes' he says: "Fixed the value of StartupDir$ string in the runtime engine so that it ends with a \ just as it does when running a program from the IDE". But that 'fix' makes StartupDir$ inconsistent with DefaultDir$ (which never has had a trailing \)!
In LBB I 'fixed' the LB 4.04 bug in the obvious way: neither DefaultDir$ nor StartupDir$ has a trailing backslash (whether run in the IDE or as a compiled EXE). I am not inclined to modify LBB to make it the same as LB 4.5, I'd rather keep it internally consistent. If you always add an extra \ in your program, for luck, it will work on all platforms because Windows accepts \\ as a valid directory delimiter.
But that 'fix' makes StartupDir$ inconsistent with DefaultDir$ (which never has had a trailing \)!
I see that there's a current discussion about this at the Liberty BASIC forum. It would be nice if Carl can be persuaded to change StartupDir$ to work the same way as LBB (i.e. for both DefaultDir$ and StartupDir$ not to have a trailing backslash, both in the IDE and when run from the run-time engine). Either way, adding an extra \ in your BASIC program is always safe.
. Does that affect the current version of LB Booster in any way? 
Logged