|   ------------------------
|   Versions: 3.2
|   Known   : Removed in Version 3.50
|
|   PowerBASIC simply forgets the Segment part of the address, that's all.
|
|   Example:
|           Demo??? = CODEPTR32(TestLabel)
|           GOTO DWORD c???
|           $SEGMENT
|           TestLabel:
|           PRINT "Test"
|           END
|
|
|   2.39. The 'ON LOCAL ERROR' Bug
|   ------------------------------
|   Versions: 3.0/3.1/3.2
|   Known   : Error corrected in Version 3.50
|
|   Using 'ON LOCAL ERROR' in a PBU can cause a crash of the program.
|
|   Example:
|           'Main file
|           $COMPILE EXE
|           $LINK "TEST.PBU"            'or PBL
|           FileName$ = "TEST.DOC"
|           CALL ResumeDemo(Demo%)
|           PRINT "Error", Demo%
|           END
|
|           'Unit file
|           $COMPILE UNIT
|           SUB ResumeDemo (Demo%) PUBLIC
|               ON LOCAL ERROR RESUME NEXT
|                 ' To test create this File with WinWord and save once.
|               OPEN "TEST.DOC" FOR BINARY AS #1
|               Demo% = ERRTEST
|           END SUB
|
|
|   2.40. ... and again 'ON LOCAL ERROR'
|   ------------------------------------
|   Versions: 3.0/3.1/3.2/3.5
|   Known   : No
|
|   PowerBASIC crashes when someone uses "ON ERROR" instead of "ON LOCAL
|   ERROR" in a SUB/FUNCTION. It can come to STACK or STRING memory
|   problems in this case, if the error occurs.
|   Of course this is definetly the error of the programmer, but the
|   Compiler should recognize this when compiling.
 
    2.41. Runtimeerror in the PowerBASIC Helpcompiler
    -------------------------------------------------
    Versions: 3.0 (Helpcompiler)
    Known   : No
    The Helpcompiler (Encoder) seems to have quitr a few Bugs. Mostly
    beginners will have some problems with Runtimeerror 9 at address
    10095. This is an internal Bug of the Helpcompile, which is caused by
    the missing of the Command '/LOOKUP'.
    2.42. The Error "Truncating" in the PowerBASIC Helpcompiler
    -----------------------------------------------------------
    Versions: 3.0 (Helpcompiler)
    The Error 'Truncating ... to 76 characters' will be shown sometimes,
    because the commandcharacters will not be taken into concern.
    2.43. Crash of the PowerBASIC-IDE after calling its own Help
    ------------------------------------------------------------
    Versions: 3.0 (Helpcompiler)
    When programming or actually the writting of the Help you will have to
    watch out that the effective length of the shown textline are not
    bigger than the actually existing number of characters available in
    the PowerBASIC-Helpwindow, because the PowerBASIC-IDE will in that
    case crash with a graphical error.
    This Bug will only occur in the developmentphase of a self-written
    Helpfile (*.PBH)!
--- CrossPoint v3.11 R
 * Origin: PBSOUND, PBFILES (40MB), PBFAQ, PBRULES, PBHIVGA at: 
2:2410/330.1)
---------------

FIDO MESSAGE AREA==> TOPIC: 214 POWER BASIC   Ref: F2200007 Date: 02/01/98
From: THOMAS GOHEL                                          Time: 12:00am
\/To: ALLE                                                (Read 1 times)
Subj: FAQ: PowerBASIC 06/16 (Coprozessor)

    =================================
    3. PowerBASIC and the CoProcessor
    =================================
    3.1. Does PowerBASIC support a CoProcessor?
    3.2. Which Floatingpointlibrary is the right one?
    3.3. Does the CoProcessor work with $FLOAT PROCEDURE, too?
    3.4. Which PowerBASIC-Functions are affected?
    3.5. Possible reasons for the CoProcessor-Effect
    3.6. PowerBASIC-Benchmark Source
    3.1. Does PowerBASIC support a CoProcessor?
    -------------------------------------------
    The answer is simply YES. The Compileroptions already have the
    possibility to choose three different Floatingpointlibraries. There
    are some Hooks when working with the CoPorcessor under PowerBASIC,
    which will be shown here so that you can develop faster hopefully only
    cleanly running programs.
    3.2. Which Floatingpointlibrary is the right one?
    -------------------------------------------------
    PowerBASIC has a total of three Floatingpointlibraries:
    a) $FLOAT EMULATE
       This is the DEFAULT-Library an usually uin use 95 % of the time.
       She has the power to automatically support the i87, if such a
       CoProcessor has been found. The huge problem is on the upper hand:
       PowerBASIC has to test for the CoProcessor all of the time and is
       slowed down a lot if NO i87 is installed.
    b) $FLOAT PROCEDURE
       This Library is fastest when no CoProcessor is available.
    c) $FLOAT NPX
       This Library is top when a i87 is available.
    3.3. Does the CoProcessor work with $FLOAT PROCEDURE, too?
    ----------------------------------------------------------
    The answer here is YES, too. Even if PowerBASIC did not implement the
    CoProcessorsupportroutines, the Source below proves that it does. The
    riddles answer lies in the PowerBASIC-Runtime-Library, which supports
    the i87 from beginning on. That is why the speed advantages can't be
    generalized.
    3.4. Which PowerBASIC-Routines are affected?