Migrating code from Turbo Basic

[Andrew Evangelidis]

I need to migrate a very old Turbo Basic program to a Power Basic Console Compiler environment. (I Know that this is old stuff! ) but i need to find out if there are any tools that can help me do this. Even if they can help me 50% of the way...then at least it will make it easier to do the rest.

[Rodney Hicks]

This is a curiosity item.
Had to check the TB manual to see if Functions and Procedures were supported it's been so long.
I suggest opening a NEW file, putting your code into the PBMAIN function, including the gosubs, but not your Functions and Procedures. Place them outside the PBMAIN function.
And then try running and see what errors are generated.
How big are these programs?
Can you post a TB file, as an attachment perhaps, so others, including myself can toy with it?

[Manuel Valdes]

Andrew:

Turbo Basic as probably you know was writen by Bob Zale, and so is more than similar to PB-DOS, in fact is almost 100% compatible.

In my own experience, to port PB-DOS code to PBCC is quite easy. Right now I am porting all my old text programs to PBCC, and my graphic PB-DOS programs to PBCC5's Graphic Window.

Regards,

Manuel

[Michael Mattias]

If the UI is just a bunch of LOCATE and PRINT statements, all you should have to change is the keyboard I-O, since PB/CC has no "INPUT" and I never saw whole lot of keyboard LINE INPUT in anyone's MS-DOS code.

i.e, it's already close to what you want.

The procedural code should be about 90% OK 'as is'.

Of course, now all you have is old code with a Botox treatment.

[Marco Pontello]

If the UI is just a bunch of LOCATE and PRINT statements, all you should have to change is the keyboard I-O, since PB/CC has no "INPUT" and I never saw whole lot of keyboard LINE INPUT in anyone's MS-DOS code.

Uh? I'm pretty sure you can find INPUT here:
PowerBASIC Console Compiler 5 - KeyWord Quick Finder

Bye!

[Michael Mattias]

>Uh? I'm pretty sure you can find INPUT here

Not fair. That was new in PB/CC 4.0.

Ok, so I should check the "what's new" more often.

MCM

[Marco Pontello]

Not fair. That was new in PB/CC 4.0.

Ok, so I should check the "what's new" more often.

Yes, just a bit. PC/CC 4.0 was introduced just some months ago.
About 48!

Bye!

[Michael Mattias]

I've been busy.

(Check my post counter if you don't believe me. You think those just "happen?" )

[Marco Pontello]

I've been busy.

(Check my post counter if you don't believe me.

I'm afraid that and "being busy" aren't necessary related.
Someone may also say they are mutual exclusive!

You think those just "happen?" )

Sometimes, yes. Sadly!

Bye!

[Manuel Valdes]

Anyway, I think even an amateur programmer should have a "formatted input" function (not using "input") instead of the plain "input" statement

[Michael Mattias]

There's only one thing which just "happens."

But we are not allowed to use that word here.

[Barry Erick]

>Uh? I'm pretty sure you can find INPUT here

Not fair. That was new in PB/CC 4.0.

Ok, so I should check the "what's new" more often.

MCM

Or just buy and use all PB programs

[Michael Mattias]

I was just starting a project today... it's for a command line utilty a client wants.

I had it started using PB/WIN 9.0.1... but after a few posts rigt here in this thread, I changed to PB/CC 5.01.

So what's the first thing that I encountered?

In 5.0.1, either STDERR changed without an "IMPROVED!" entry in the help file or a note in history.txt, or the help file was not fixed even though support told me two months ago the bug I found was in the help file, not the compiler.

(Thru 5.0.0, STDERR isnot redirectable, help file statements notwithstanding)

When I use PB/Win for these, I have to use my own STDOUT and STDERR functions. I know how those work.

But I'm gonna tough it out with CC for this piece of software anyway.

MCM
PS: Workaround here: Redirect 'stderr' to a file with PB/CC November 2008