Picbasic Pro compiler 2.60 error

[Luckyborg]

I recently loaded a program that I had compiled with v 2.47 with no problems, when I tried compiling with 2.60 I get a "fatal: out of memory (pbpw.exe)", this is after microcode studio reports it is not responding. When I switch back to 2.47 all compiles fine.

Here is the line that causes the problem

in_stream   var byte[20]

    write 1, (in_stream[0] - " ")  

End

as a side note when I changed the "-" to "+" I do get other compiler errors about mismatched array delimeters (]

I am fairly confident the code worked as expected originally. I can fix the problem with a temp variable then "write 1, temp", but wanted to see if this is a real error with the compiler or am I just not understanding what I'm doing

Thanks
David

[Kamikaze47]

does it still give you errors if you change it to this?

WRITE 1,(in_stream[0]-32)

[Darrel Taylor]

Just remove the outer parenthesis and it should work.

Make sure you have another WRITE somewhere in your program that writes a BYTE without any formulas.
It doesn't have to actually execute, but it needs to be somewhere in the program.
<br>

[Luckyborg]

Thanks for the replies.

does it still give you errors if you change it to this?

WRITE 1,(in_stream[0]-32)

yes it does

DTs two comments were both required to get it working.

Do you know is this considered and error that will be fixed in future releases? It seems like you should be able to have any number of parenthesis (within reason) as it previously did in 2.47 and the extra write statement seems like a clever patch, but definitely you should never have to write code that won't be used to make other code work. It is good to know how to solve the problem. Hopefully this thread will help someone else, though I am pretty sure I have read your write one byte comment in a previous thread a long time ago and just forgot all about it until you restated it. As always thanks for the help.

David

[Darrel Taylor]

They are known issues with PBP 2.60.

The EEPROM commands were modified considerably to allow WORDs and LONGs.
A couple errors crept in, and they are supposed to be fixed in the next patch.

Keep an eye on this page ...

Known issues in PICBASIC PRO Compiler 2.60
http://melabs.com/support/pbpissues.htm
<br>

[Acetronics2]

Hi, Darrel

I catch the thread in flight ...

As you have somewhat modified the PbP files ( DT Goodies i.e. ...) there should be a little problem with patches ( ??? corrected wayyyyy before the patch comes, I suppose ....) and upgrades ...

For us ... patch refuses to apply if files have been modified, so we get a brand new full installation !!!

How do you proceed not to loose or forget the mods each time a new upgrade comes ???

Alain

[Ioannis]

ehhmmm,... make notes in a notepad maybe???

Yeah this is an issue that bothers me too. I got 2.50 but never replaced my old installation just because I am lazy to find which files I modified...

Ioannis

[Acetronics2]

ehhmmm,... make notes in a notepad maybe???

Hi, Ioannis

May we suppose it's new year Humour ...

ROFL

Alain

[Ioannis]

Alain, we need it don't we?

If you think any way of mking updates less painful, do tell us.

When Darrel wakes I am sure he would give an idea on this.

After all I bet he has the most modified PBP directory!

Ioannis

[Luckyborg]

Maybe instead of using the word "patch" I should have said "band-aid solution"

the patch I was referring to would be in my files, not the compiler files. ie a

write 0,0

at the end of the program that never gets called.

David

[Darrel Taylor]

For us ... patch refuses to apply if files have been modified, so we get a brand new full installation !!!

When Darrel wakes I am sure he would give an idea on this.
After all I bet he has the most modified PBP directory!

Oh hello, I'm awake now. 10PM

Actually, for each patch or version level, I create another whole installation from the CD, then apply the patch.
That way I can test for people's problems related to the specific version/patches.

Talk about a mess ...
I've got 9 PBP folders. Each one with different levels of modification.
I'm constantly commenting out config lines in .inc files.

I guess, for anyone that only wants one installation, the procedure is the same. (Patch a clean installation)
Just delete the old installation when you're finished. NOT

But some day ... you'll want something that was in that folder.
Some day will be 3-days after you delete it.

How do you proceed not to loose or forget the mods each time a new upgrade comes ???

I don't. I figure it out again when something doesn't work.
Cause it may be for a different reason now.
<br>