Arrange for the interpreter to ignore the #! in the first line

[pentalive]

If somehow the interpreter would ignore #! which pcbasic as the first line - PC basic programs would become click launchable. On should then be able to just find MYPROG.BAS in the file manager of one's choice and double click it - pcbasic launches with the MYPROG.BAS as a command line argument, and the basic program there in runs. If the basic program ends with a SYSTEM statement, then the app becomes just like any other app on that Linux box.

When saving a program it should add that #! above.

[robhagemans]

Hi, thanks for the suggestion - I don't think I'll implement this though, for a few reasons

• it breaks compatibility with GW-BASIC - any program not starting with a line number should fail with a Direct statement in file
• the shebang line is for shell-scripts, and the GW-BASIC language is really quite unsuitable for shell scripting
• it's a bit of a niche, OS-specific feature, which means it's a pain for documentation, support and maintenance

[pentalive]

Hey Rob! Thanks for your rely. I understand totally - It's great to have GWBASIC again on my Linux Box.

…

------------------------------------------------------------------------------------------------- Ronald Hudson.

Sent from my Linux Laptop

________________________________ From: Rob Hagemans ***@***.***> Sent: Friday, October 21, 2022 11:37 PM To: robhagemans/pcbasic ***@***.***> Cc: Ronald Hudson ***@***.***>; Author ***@***.***> Subject: Re: [robhagemans/pcbasic] Arrange for the interpreter to ignore the #! in the first line (Discussion #216) Hi, thanks for the suggestion - I don't think I'll implement this though, for a few reasons * it breaks compatibility with GW-BASIC - any program not starting with a line number should fail with a Direct statement in file * the shebang line is for shell-scripts, and the GW-BASIC language is really quite unsuitable for shell scripting * it's a bit of a niche, OS-specific feature, which means it's a pain for documentation, support and maintenance — Reply to this email directly, view it on GitHub<#216 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADBF2FNGHXYZ3G4YI4GUC3LWEODRNANCNFSM6AAAAAARKRRNCM>. You are receiving this because you authored the thread.Message ID: ***@***.***>