Turbo basic xl and compilers question

[eegad]

Always liked turbo basic xl. My only wishlist feature would be a way to compile a program to a standalone binary. Unfortunately it can only compile to a .ctb file which then gets run with runtime.com. What I was wondering is if there might be a way to sort of "append" a ctb file to the runtime.com, thus creating a standalone in a roundabout way. I mean if runtime is loaded into memory, and the ctb gets loaded into memory and then executed, why can't you possibly just load it as one chunk (depending of course on where it gets loaded....I assume you couldn't do this if the runtime resides in the ram under the os). Any thoughts?

 

Also, are there any other compilers other than abc and mmg? (would like convert an old basic program into an executable, but it does use floating point, and it does have variable goto's, so abc/mmg are out)

[baktra]

I can provide some alternative for you question #2. Apart from compilers, there are also Atari BASIC "embedders" that will simply encapsulate an Atari BASIC program in a binary load file. There are no speed enhancements, of course.

http://atariage.com/forums/topic/215992-basic-to-xex-compiler-that-keeps-original-basic-speed/?hl=%2Bbcom&do=findComment&comment=2817639

[Roydea6]

http://atariage.com/forums/topic/116416-need-compiled-turbobasic-linker/?p=1405502

[thorfdbg]

Always liked turbo basic xl. My only wishlist feature would be a way to compile a program to a standalone binary. Unfortunately it can only compile to a .ctb file which then gets run with runtime.com.

While others have answered - wow, I did not know that there was a Turbobasic linker - the result file is rather lengthy, and the compiler never reached the quality of the TurboBasic interpreter itself. It had numerous bugs, unfortunately.

 

What I would recommend is the ABC "compiler" for Atari Basic (not Turbo Basic), which comes with a rather slim runtime (less than 4K). The important part is maybe that it has found some commercial use, so it is a proven working compiler.

 

The drawback is that it only supports integer math, and it does not really "compile" anything. It rather transforms the program into pseudo-code which is then interpreted by the runtime. Yet, the result is quite fast.

[+JAC!]

Question is why you really want a single .XEX. Both TBXL and the Runtime support autstart, so for most cases you don't even see a difference.

[thorfdbg]

Question is why you really want a single .XEX. Both TBXL and the Runtime support autstart, so for most cases you don't even see a difference.

Because you won't be able to run such a construction from a game dos.

[eegad]

I'll give ABC another look. I'm pretty sure the program in question does some non-integer math, but I'll give it a shot and see what happens.

 

As to the reason why I want it as a single compiled file is that I'd like to put it on one of my MaxFlash carts and be able to use it on a real 800xl without the need for using (and waiting for) a disk drive. The program runs too slow in standard Atari Basic....it runs just fine in Turbo Basic.....but Turbo Basic won't load with MaxFlash Carts (I assume they both use the same portion of ram under the os...if anyone knows of a way to get TurboBasic running on a MaxFlash cart, PLEASE let me know - that would solve my problem quite nicely).

[+Larry]

ABC is very nice! Not too difficult to work around the integer issue.

 

Look here, and I'm pretty sure you'll find the manual. Explains work-arounds.

 

Larry

[+CharlieChaplin]

Well,

 

if RAM under the OS is a problem for your or your flashcart, then CTB or Runtime+CTB linked into one single/stand-alone XEX file will not help you - because the CTB Runtime also uses RAM under the OS (and the CTB-runtime is part of the linked XEX file)...