home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Power-Programmierung
/
CD1.mdf
/
basic
/
library
/
pb
/
library2
/
readme
< prev
next >
Wrap
Text File
|
1990-03-31
|
3KB
|
63 lines
PowerBASIC Patch Documentation
==============================
The PowerBASIC patch programming utility (PBPATCH.EXE) is provided to
allow you to install modifications, bug fixes, and enhancements to the
two PowerBASIC compilers (PB.EXE and PBC.EXE). It is only to be used
in conjunction with patch data files issued by the developers. When
executed, it will directly modify the compiler files, to add the needed
modifications. It is important that you only modify a copy of the
compiler files, not an original master, as it is possible that the
patch process may not be successfully completed (you might experience
a disk read/write error, power outage, etc.), and the resulting
"partially-patched" compilers would be unusable.
PowerBASIC patch data files are identified by a simple naming convention,
PBnnnnnn.PAT, where nnnnnn represents the issue date of the patch file.
Thus, a file issued on January 1, 1990 would be named PB010190.PAT.
This is version #1.1 of the PBPATCH utility, and may be used with patch
data files issued on or after 3/30/90, and until a later PBPATCH version
is issued. When executed, PBPATCH will verify the compatibility of the
patch data file, and report any inconsistency.
To execute the patch utility, place one or both of your compiler files
(PB.EXE and PBC.EXE) in your default directory, and then just execute
PBPATCH.EXE. An initial prompt will ask you to identify the patch data
file to be used. Enter the data file name, and PBPATCH will do the rest.
=========================================================================
=========================================================================
3/30/90 --- PowerBASIC patch data file: PB033090.PAT
This patch data file is usable only with PowerBASIC (PB.EXE and PBC.EXE)
Rev. #2.00B. It provides the following enhancements and/or corrects the
following error conditions:
1. References to public procedures (GET$LOC, GET$LEN, etc.) may not
link correctly, when referenced in a chained file.
2. CVF function may not execute correctly in an .EXE file.
3. CBCD function may not execute correctly in an .EXE file.
4. Single line DEF FN's which return BCD type may not execute correctly
in an .EXE file.
5. An "Out of Memory" error is sometimes generated incorrectly and/or
prematurely when compiling to disk files.
6. Single Precision FUNCTIONs and DEF FN's may return an incorrect
result or cause side effects in procedural mode.
7. ARRAY INSERT and ARRAY DELETE return incorrect error codes.
8. FIELD will not accept multiple FROM x TO y syntax.
9. Display of free memory available may be inaccurate.
10. REMOVE$ function and REPLACE statement may not function correctly.