Microsoft Quick Basic 7.1安装版

README.DOC File

Release Notes for Microsoft (R) BASIC Professional Development System

Version 7.10

(C) Copyright Microsoft Corporation, 1990

Product Serial Number: 00-007-2710-00007050

This document contains release notes for version 7.10 of the Microsoft (R)

BASIC Professional Development System for MS-DOS (R) and the Microsoft

Operating System/2 (MS(R) OS/2). The information in this document is more

Microsoft revises its languages documentation at the time of reprinting,

so some of the information in this online file may already be included in

your manuals.

=======================================================================

Contents

=======================================================================

Part Description

---- -----------

1 Notes and Tips

2 Notes for "Microsoft BASIC Language Reference"

Quick libraries created with version 7.1 that use the LBOUND or UBOUND

functions or the ERASE statement on a dynamic array whose elements include

a record containing a static array will not work with version 7.0 of QBX.

Compatibility with Novell Netware

-----------------------------------

If you have a peripheral (such as a mouse) that uses Interrupt Request

Level (IRQ) 3, and your system is part of a network using Novell (R) Netware

version 2.15 or earlier, your system may hang when you load QBX, PWB, or

CodeView. As a temporary solution, set your peripheral to use another

interrupt. For more information, contact your Novell Netware dealer.

MSHELP.DLL must be located in the path set by LIBPATH in your CONFIG.SYS

file in order to use Help in PWB under OS/2.

NMK Utility

-----------

The NMK utility (NMK.COM) should not be used within PWB. To get help on

NMK, type QH NMK from the command line.

ILINK and BIND Utilities

------------------------

Documentation for the ILINK and BIND utilities is included online for

compatibility with Microsoft C. These utilities are not included with

Microsoft BASIC and are not supported by BASIC.

I/O within LPRINT, PRINT #, PRINT # USING, WRITE, and WRITE USING

argument to the statement that will perform the output. In the following

example output will always go to the screen:

OPEN "Test1.dat" FOR INPUT AS #1

OPEN "Test2.dat" FOR OUTPUT as #2

PRINT #2, INPUT$(10, #1)

The following rewritten example will send output to the proper place:

OPEN "Test1.dat" FOR INPUT AS #1

OPEN "Test2.dat" FOR OUTPUT AS #1

TEXT$ = INPUT$(10, #1)

PRINT #2, TEXT$

Output is also sent to the screen if you use an argument that is a

user-defined function that also performs input/output. You must not

2. Set the LINK environment variable to include the /CO (CodeView) option.

After you run BUILDRTM, you should set the LINK environment variable back to

its original setting.

References to Version Numbers in Filenames

------------------------------------------

The references to the filenames for the BASIC run-time libraries and run-

=======================================================================

Page Section\Note

31-32 CALL (BASIC Procedures)

-----------------------

In version 7.1, BASIC supports the use of the BYVAL keyword

in CALL, DECLARE, SUB, and FUNCTION statements for BASIC

procedures. You can use BYVAL to pass parameters by value

rather than by reference (the default). It is no longer

necessary to enclose parameters in parentheses to emulate

passing by value. For more information and an example of using

BYVAL in BASIC procedures, see the online Help for the DECLARE

CALL, see the online Help for the CALL statement (BASIC

37 CHAIN

-----

Under DOS 2.1, CHAIN will not work unless filespec$ provides a

path. Also under DOS 2.1, if the run-time module is in the

root directory, the root directory must be listed in the PATH

environment variable.

40 CHDIR

Refer to the online Help for CHDIR for a more appropriate

example of CHDIR and MKDIR usage.

61 COMMAND$

--------

The fifth line from the top of the page is missing a pair of

parentheses. The line should read:

however, still use 1 and 2 within the QBX environment.

84 DATA

You cannot use ASCII 01 and 02 in data strings if

you are going to compile to an executable program.

See the preceding note for CONST.

88 DECLARE (BASIC Procedures)

--------------------------

In version 7.1, BASIC supports the use of the BYVAL keyword

Be careful when using the SEG keyword or when passing parameters

by near reference (no keyword), because BASIC may move variables

in a CALL statement's argument list that causes memory movement

may create problems. You can safely pass variables using SEG or

near reference if the CALL statement's argument list contains

only simple variables or arithmetic expressions. SEG cannot be

used to pass arrays.

116 END

---

Syntax 2, END [n%], accepts a range of integers from -32,768

through 32,767, inclusive.

144 FUNCTION

147 GET (File I/O)

--------------

The argument for record number should be "recordnumber&" since

it accepts a long-integer value.

151 GET (Graphics)

--------------

Screen modes 3 and 4 should be added to the table at the top of

one plane.

177 KEY (Assignment)

----------------

The KEY n%, stringexpression$ syntax can also be used to

create user-defined keys. Refer to the information on page 180

for specific details on how this is accomplished.

middle of the page should mention that only the first five

(12 decimal) for non-extended keyboards and &H8C for extended

keyboards.

-------------------

Add the following to the Keyboard Scan Code chart:

Key Code

--- ----

F11 133

F12 134

238-239 OPEN COM

--------

Ready (DSR) line does not work properly. In this case, you

will have to either not ignore the DSR line or you will have

to jumper the DSR line to an active high-signal line. Refer to

serial port information that specifically pertains to your

hardware, and perform any modifications at your own risk.

The range for the parity argument should include the value PE.

Setting parity to PE enables parity error checking.

261 PLAY (Music)

The remarks should note that the PLAY statement generates an

The syntax for the PRINT USING statement should be as follows:

PRINT USING formatstring$; expressionlist [;]

The PRINT USING statement does not use print zones. You cannot

replace the optional semicolon with a comma.

------------------------

The argument for record number should be "recordnumber&" since

it accepts a long-integer value.

The introduction to the example near the bottom of the page

incorrectly states that "the following two statements write

15 bytes to file number 1:" The example actually writes 17

must use halloc() and hfree().

The corrected C code for the SETMEM example is as follows:

void far cfunc(bytes)

int bytes;

{

char *halloc();

char *workspace;

/* Allocate working memory using amount BASIC freed. */