Search Results - MEL PICBASIC Forum


Search:

Type: Posts; User: pedja089; Keyword(s):

Search: Search took 0.00 seconds.

  1. Replies
    29
    Views
    78,504

    Re: Better code check before compile?

    Same here :confused:
  2. Replies
    29
    Views
    78,504

    Re: Better code check before compile?

    From manual

    2.18 Line-Concatenation ( : )
    Multiple commands may be written on a single line using colon characters to tell PBP where to insert a "virtual" line break.
  3. Replies
    29
    Views
    78,504

    Re: Better code check before compile?

    Hehe. Read manual...
    This : replaces new row. Same as you press enter on your keyboard. So try to compile code from my code above. You will get same results.
    Only thing behind THEN depending on IF....
  4. Replies
    29
    Views
    78,504

    Re: Better code check before compile?

    That is not bug. That way should work. This : is same as new row.
    So this line

    if ticker>150 and ard<140 and atrig=0 then ticker=1: atrig=1

    is same as this


    if ticker>150 and ard<140 and...
  5. Replies
    29
    Views
    78,504

    Re: Better code check before compile?

    That is exactly what I have on my mind in post #8.
    Maybe it will be useful if compiler give just warning about missing RETUN.
    But That wouldn't prevent bad stuff from happening same as it throwing...
  6. Replies
    29
    Views
    78,504

    Re: Better code check before compile?

    Then 80% of my programs wouldn't compile. I often use multiple entry point in same sub. And have only one return at end.
  7. Replies
    29
    Views
    78,504

    Re: Better code check before compile?

    If your code can start fire, you are doing something really wrong.
    For first run, always use PSU with limited power(at least current limiting) with no load at output. Move actuators if you have...
Results 1 to 7 of 7