PB/CC

What is PB/CC?

PB/CC is a 32-bit Native Windows compiler, by PowerBasic Inc.
To a novice, it may not appear like a windows application: it has no build-in GUI instructions, but operates stricktly through the Windows console, which has the look & feel of a DOS application.

The History Of PB/CC

1998	-	PB/CC 1.0 is released. Primarily marketed at existing PB/DOS users, as an easy way to port their existing DOS applications into the world of 32-bits Windows.

1999	-	PB/CC 2.0, a major update Adding TCP/IP, Regular Expressions, COM-support (Serial Communications), and a lot of other features.

Why should I use PB/CC?

In certain situations, a Console screen has definite advantages over a GUI-based application: since it's keyboard- rather then mousebased, it's often preferred for data-entry. Certain automated tasks simply don't need a GUI - with PB/CC, you don't have to worry about this. Third, it is as close as you can get to PB/DOS in a 32-bit windows environment. Build-in support for the elementary PRINT, LOCATE, COLOR (and similar) statements, this is the easiest windows programming language to convert your existing DOS-code into.
But why bother, since those DOS programs run fine under Windows anyway?

Even though it might seem otherwise to the laymen's eye, a console application is a true windows application. In a world where DOS is fading into the background, this will give you a little more certainty about future compatibility of your programs.
Also, a 32-bits windows program runs much more stable then a 16-bits DOS session under Win95, and is much less demanding on system resources. Finally - a console application has full, unrestricted access to the entire Win32 API, allowing you to unleash the power of Windows.
Will I be able to use my old PB/DOS code?

It depends entirely on your programs: PB/CC offers the basic textmode commands. Console windows do NOT support any graphics at all, so any of your programs that may use graphical screenmodes won't be able to run under PB/CC. Furthermore -- direct access to hardware is much more resticted under Windows. If your programs use a lot of low-level hardware access, you will experience difficulties as well.

Apart from these issues, PB/DOS code can be ported with only minor modifications.
Any Future Plans?

No official statements have been made, but it is rumored that a LINUX port of PB/CC is a might be a possibility in the future. Of course the Windows-specific API access won't work on a unix platform, but the basic functionality should be portable.

There are no certainties on what the future may bring, but... who knows?

Last Updated: 24 May 1999