Mostly because some things work just a little differently than they used to.Originally Posted by Joe S.
Programs that you've written before, may compile fine with the new version, but may not work exactly the way it would if compiled with the 16-bit version (PBPW.EXE).
Sometimes it's just little things, like MAX and MIN, or math formulas that you expect to have one result after Overflowing, but it doesn't overflow anymore. Or maybe an IF statement that didn't consider negative numbers when it was first written.
So for anything written for 2.47 or prior, it's a good idea to compile it with PBPW.EXE (2.50)
And if you want to use longs. Make a new program. If you just try to insert longs in your old programs ... well I guess at least we'll have lots of problems to talk about on the forum .
The other part is that PBPL.EXE will generate programs that are larger than PBPW. Most of the System Functions are set up to use LONG variables. Even if you don't use LONGs in your program, it still takes up the extra code space. Plus all T? variables (the temporary variables use in complex math formulas) are all LONGs, as are R0-R3, so it uses more RAM too.
Charles Linquis recently reported that his program which used to fit in 128k, doesn't anymore.
What a Code HOG.
He also estimated the increased size at 5%.
Seems pretty low to me. I would have expected more.
Then there's that 18F only problem that you pointed out.
<br>
Bookmarks