Pbp3


Closed Thread
Results 1 to 22 of 22

Thread: Pbp3

Hybrid View

  1. #1


    Did you find this post helpful? Yes | No

    Default Re: Pbp3

    Hello everybody.

    I wonder if anyone has had experience aa compile a program with PBP3. I wonder if a program previously compiled in version 2.5 can have your code when compiling with reduced PBP3.

    I wait for answers ...

  2. #2
    Join Date
    Sep 2004
    Location
    montreal, canada
    Posts
    6,898


    Did you find this post helpful? Yes | No

    Default Re: Pbp3

    Hi and Welcome on the forum,
    Not sure to understand your question, I feel a sort of language barrier in here. No problem, so let me guess.

    Yes a code compiled in PBP 2.50 will also compile with PBP3, BUT if it's USB, you'll need to modify it to suit the next USB requirement since v2.60.

    Reduced PBP3... this one I'm not sure of what you mean.. There's the full demo version which work for 30 days, this one no problem. But there's also The Gold and Experimenter version who have their limitations listed in the following link when you click on the Compare Edition tab.
    http://store.melabs.com/cat/PBP.html

    HTH
    Steve

    It's not a bug, it's a random feature.
    There's no problem, only learning opportunities.

  3. #3
    Join Date
    Oct 2005
    Location
    Sweden
    Posts
    3,610


    Did you find this post helpful? Yes | No

    Default Re: Pbp3

    Hi,
    You mean if PBP3 is more efficient, producing smaller code than earlier versions?

    My current project compiles to the exact same size (currently around 12k) between 2.6 and 3.0, no difference at all. I don't have 2.5 on my system so I can't compare.

    /Henrik.

  4. #4


    Did you find this post helpful? Yes | No

    Default Re: Pbp3

    Thanks Henrik, this is my doubt...

  5. #5
    Join Date
    May 2008
    Location
    Italy
    Posts
    825


    Did you find this post helpful? Yes | No

    Default Re: Pbp3

    Question!

    Page 58 of PBP3 manual state that DEFINE statement and all parameters associated should be always in upper case.

    This should be read: " with the exeption of the define statement ", since microcode editor turn the word DEFINE into lower case.

    Is the above correct?


    Al.
    All progress began with an idea

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


    Did you find this post helpful? Yes | No

    Default Re: Pbp3

    MicroCode Studio only changes the case that is viewed in the editor.
    The characters saved to the file are exactly as you typed them.

    But DEFINE is a PBP statement, and PBP is not case sensitive, so it doesn't matter how you type the actual word DeFiNe.
    What comes after DEFINE is passed to the assembler unchanged and MPASM is case sensitive.
    Any defines that PBP will be looking for are all UPPERCASE, so anything after DEFINE should be all UPPERCASE.

    If you are using defines in your own assembly language code then anything after DEFINE must match the case that your ASM code is looking for. Those do not have to be uppercase, but it makes things easier if you stick with the standard convention of all uppercase.
    DT

  7. #7
    Join Date
    Aug 2005
    Posts
    95


    Did you find this post helpful? Yes | No

    Default Re: Pbp3

    Just a query regarding deactivation of picbasic pro3, you say you have the ablity to deautherise a computer so you can move your copy of picbasic pro to another. But what happens when the computer has a hardware faliure. How do you deautherise that computer.

    Thanks Sphere.

Members who have read this thread : 0

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