Error

[tekdavid]

i am using picbasic and this should work but it dont can any one tell me were my error is in program fornext

error fornext.bas,12: ':' or '=" expected (token 'var')
error fornext.bas,13: variable expected (token 'i')
error fornext.bas,17: next without maching for




12: i VAR byte
13: for i = 1 to 4
14: high 0
15: pause 1000
16: low 0
17: next i

[Melanie]

The clue is the common denominator for lines 12, 13 and 17... it doesn't like your variable.

I don't have PICBasic, only PICBasic Pro, however, whilst your code would be valid in PBP, in PBC I believe the variables are predefined... you must use them, although (and I stand to be corrected) you might be able to alias them... try this as a starter...

for B0 = 1 to 4
high 0
pause 1000
low 0
next B0

Consult the PBC manual for variables.

[bartman]

You do have to use the pre-assigned variables as mentioned here or use this at the beginning:

i symbol B0

to assign your own name to the variable.

Bart

[Dwayne]

Hello tekdavid,

TD>>12: i VAR byte
13: for i = 1 to 4
14: high 0
15: pause 1000
16: low 0
17: next i<<

I also question lines 14 and 16...

Usually it is a High Porta.0 or Low Porta.0 or
it may be High Portb.0 or Low portb.0

Either way, It might be good to assign a port to it.

Another problem... What do your lines BEFORE line 12 look like?
Sometimes the compiler may flag line 12, but the problem is actually
in line 10 or 11....

Dwayne

[Melanie]

I think it's the illegal (undeclared) variable 'i' in this case Dwayne...

High 0 and Low 0 are valid for addressing pin 0 of your PIC (note that which physical pin that pin 0 refers to is dependant of the PIC family - refer to the PICBasic manual for that).

[Dwayne]

Hello Melanie,

Melanie>>High 0 and Low 0 are valid for addressing pin 0 of your PIC (note that which physical pin that pin 0 refers to is dependant of the PIC family - refer to the PICBasic manual for that).<<

Gotcha...I wasn't sure which pic they were using...

I always seem to get myself into trouble if I don't spell it out <smile>.. Thus I kinda do things the "long Hand" way...GPIO.0, Porta.0, or whatever. Its kinda like those headers at the beginning of your file, If it is already defined for your chip, it can save *ME* a lot of time trying to figure out why my compiler is burping at me.