Determining LONG compiler


Closed Thread
Results 1 to 3 of 3
  1. #1
    Join Date
    Sep 2005
    Location
    Campbell, CA
    Posts
    1,107

    Default Determining LONG compiler

    In the 2.6x versions of the compiler, you set a switch to choose PBP or PBPL.

    If there were no LONGS in your pogram, you could still compile with PBPL, and it didn't tell you.

    I think I remember someone telling me that I could put an ASM block - something like

    ASM

    ifdef PBPL_USED
    LIST
    ....
    NOLIST
    endif

    ENDASM

    But I can't remember the details. Could someone please refresh my (failing) memory on how to detect if the PBPL compiler has been used, or block it from compiling at all if I try to use PBPL?
    Charles Linquist

  2. #2
    Join Date
    Jul 2003
    Location
    Colorado Springs
    Posts
    4,959


    Did you find this post helpful? Yes | No

    Default Re: Determining LONG compiler

    PBP 2.50/2.60/PBP3
    Code:
    ASM
        if ((R1-R0) == 4)
            error "Compiled with PBPL"
        endif
    ENDASM
    PBP3 only (faster)
    Code:
    #IF __LONG__ = 1
        #ERROR "Compiled with PBPL"
    #ENDIF
    The second one is faster because PBP picks up the error.
    The first one has to go through the assembly process before you get the error.
    DT

  3. #3
    Join Date
    Sep 2005
    Location
    Campbell, CA
    Posts
    1,107


    Did you find this post helpful? Yes | No

    Default Re: Determining LONG compiler

    So my next question is --

    Is there some trick that I can use that will automatically invoke PBP if no LONGs are declared, and invoke PBPL if they are?
    Charles Linquist

Members who have read this thread : 1

You do not have permission to view the list of names.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts