Hardware Reference
In-Depth Information
Figure 6.1 The Microsoft BASIC Professional Development System IDE
hardware directly are unsuitable for deployment in a Windows Protected Mode
environment . In order to overcome the restrictions imposed by later versions of
Windows (i.e. beyond Windows 9x), your applications may have to be prepared
with a view to operation in a pure DOS environment (rather than in a DOS
Window). We will return to this important point later in this chapter.
Many of the BASIC programs that appear in this topic were originally
developed using QuickBASIC and Microsoft BASIC 6.0, and most are compat-
ible with modern forms of BASIC (such as QBX and PowerBASIC 3.5). The
early Microsoft DOS BASIC packages provide the user with a simple 'no-frills'
Integrated Development Environment (IDE) (see Figure 6.1). The IDE allows
program entry, editing, running, and debugging without having to leave the
IDE's shell. Programs can be tested during development with minimal fuss and
then free-standing executable programs (EXE files) can be produced when the
user is reasonably confident that the program is robust and bug-free.
Microsoft DOS BASIC also offers the user comprehensive context-sensitive
online help. Using the resident BASIC text editor, syntax errors are reported
immediately when the code is entered, and debugging is aided by the availability
of breakpoints and watchpoints which can be freely imbedded within the code.
Modular programming is encouraged and current modules are co-resident
in memory during program development. Multiple editing Windows allow the
programmer to view the main code along with the code for a subprogram (pro-
cedure). The programmer can also exit to DOS, carry out a DOS operation
(such as formatting a disk) and then return to the BASIC environment at the
point at which it was left.
Despite its age, Microsoft DOS BASIC can still provide a useful environment
for developing simple and compact DOS-based applications. So, as long as you
Search WWH ::




Custom Search