Run code without compiler

[phil 9.0]

Hi 

I'm relatively new to coding at age 67 and have downloaded QB64PE however I seem to have a problem running code without the compiler creating a <.exe file> even though I select run only (No exe) Can anyone give advice of what maybe the cause? I'm using edition 3.14.1 on windows 10 with latest update

Thanks

[bplus]

Bas code has to be compiled to run. It runs through a conversion process to C and the exe made from that.

I haven't looked at that menu carefully for ages, I can see why you might think QB64pe is still an Interpreter from that but it's not. I have no idea why it would say No exe, that's silly. The first thing it says below is "Creating EXE file..." when you choose that option, crazy!

Qb64 has been compiled since day 1 of it's existence independent of DOS.

So welcome to the forum, anything else we can't help you with

BTW I am not liking the slow typing of my code and the double click needed of an already selected item of version 3.14.1 it's very distracting, we are going backwards in progress.

[bplus]

BTW @phil 9.0 the first time(s) you use QB64PE the complile time is much longer than usual.

If you stick with QB64PE you will grow accustomed to compile time and love all the new stuff since whatever earlier experience of QB you have.

[SMcNeill]

run only (No exe) should create a temporary EXE to run and then delete it when it's finished.  Its purpose is to just help keep your file folders clean, without clogging them up with EXE files that you don't really care about keeping around (like code snippets for testing from the forums and such).  

I suppose there's always the chance that your system has a weird set of permissions assigned to it where you can write files (and create new ones), but not delete them, and that would defeat the "Run only (No Exe)" purpose.   

But QB64 and QB64PE are both nothing more than translators that translate your BAS code into C code, and then we use the gcc compilers to make that an executable which is then ran.   "Run only" just cleans up and doesn't leave that exe behind (No exe), once it's finished doing whatever it does for you.

[Pete]

Finally a youngster on the boards. I'm almost not kidding. A lot of us here are from the QBasic generation, AKA QJurassic Age. I have to admit I never thought I'd be happy with a system without an interpreter to test code without compiling it first, but I got used to leaving that behind years ago. As bplus mentioned, the first compilation takes a much longer time than subsequent compilations. After the initial one, any edits to your code will get compiled pretty fast. Now you may miss stepping through the code, but if you look at the F4 debug option, there are some tools there to do just that.

Welcome, and feel free to post any code, or ask any code related questions. Most of us are veteran coders but we are happy to help. Remember there are no such things as stupid questions, only stupid people... and Clippy isn't here anymore so that solves that.

Pete

[PhilOfPerth]

Welcome. @ phil9.0
I'm version 1.1 of the Phil species (dinosaur age)!
Yes, that menu option is confusing; I fiddled with it for a while then shelved it, and never felt the need to get it sorted. Other options cover everything I need to produce meaningful (to me, anyway) progs easily and quickly.
Incidentally, I wonder should we call version 3.14.1 the Pi version ? 
Have fun with it!

[phil 9.0]

Bas code has to be compiled to run. It runs through a conversion process to C and the exe made from that.

I haven't looked at that menu carefully for ages, I can see why you might think QB64pe is still an Interpreter from that but it's not. I have no idea why it would say No exe, that's silly. The first thing it says below is "Creating EXE file..." when you choose that option, crazy!

Qb64 has been compiled since day 1 of it's existence independent of DOS.

So welcome to the forum, anything else we can't help you with

BTW I am not liking the slow typing of my code and the double click needed of an already selected item of version 3.14.1 it's very distracting, we are going backwards in progress.

Thanks 

---

Welcome. @ phil9.0
I'm version 1.1 of the Phil species (dinosaur age)!
Yes, that menu option is confusing; I fiddled with it for a while then shelved it, and never felt the need to get it sorted. Other options cover everything I need to produce meaningful (to me, anyway) progs easily and quickly.
Incidentally, I wonder should we call version 3.14.1 the Pi version ? 
Have fun with it!

Thanks 

---

Finally a youngster on the boards. I'm almost not kidding. A lot of us here are from the QBasic generation, AKA QJurassic Age. I have to admit I never thought I'd be happy with a system without an interpreter to test code without compiling it first, but I got used to leaving that behind years ago. As bplus mentioned, the first compilation takes a much longer time than subsequent compilations. After the initial one, any edits to your code will get compiled pretty fast. Now you may miss stepping through the code, but if you look at the F4 debug option, there are some tools there to do just that.

Welcome, and feel free to post any code, or ask any code related questions. Most of us are veteran coders but we are happy to help. Remember there are no such things as stupid questions, only stupid people... and Clippy isn't here anymore so that solves that.

Pete

Thanks 

[phil 9.0]

Welcome. @ phil9.0
I'm version 1.1 of the Phil species (dinosaur age)!
Yes, that menu option is confusing; I fiddled with it for a while then shelved it, and never felt the need to get it sorted. Other options cover everything I need to produce meaningful (to me, anyway) progs easily and quickly.
Incidentally, I wonder should we call version 3.14.1 the Pi version ? 
Have fun with it!

Had a little chuckle myself when I noticed the version Nr, Thanks 

---

run only (No exe) should create a temporary EXE to run and then delete it when it's finished.  Its purpose is to just help keep your file folders clean, without clogging them up with EXE files that you don't really care about keeping around (like code snippets for testing from the forums and such).  

I suppose there's always the chance that your system has a weird set of permissions assigned to it where you can write files (and create new ones), but not delete them, and that would defeat the "Run only (No Exe)" purpose.   

But QB64 and QB64PE are both nothing more than translators that translate your BAS code into C code, and then we use the gcc compilers to make that an executable which is then ran.   "Run only" just cleans up and doesn't leave that exe behind (No exe), once it's finished doing whatever it does for you.

Thanks