Looks like it is definitely a bug (I have bought one week ago the 3.1 update to be sure).
I'm writing in the bug report section of Melabs to see what they say. Here.
Thanks
Looks like it is definitely a bug (I have bought one week ago the 3.1 update to be sure).
I'm writing in the bug report section of Melabs to see what they say. Here.
Thanks
you should verify the 3.1 version does the same thing , i used 3.0.10
i expect it will , the space shuttle was still a thing the last time the pbp core routines were enhanced
Warning I'm not a teacher
I was using 3.0 and bought 3.1 update to see if it was solved, but not.......
I think I will start to work on my subroutine to avoid use of string modifiers, though they are very powerful, it's a pity.
be wary any pbp command that uses jumpman the same way will probably fail , there may be other avenues of failure possible too
Yeah, until you here from Charles I'd be very careful with pushing the library routines beyond the 64k barrier.
I did compile the code and I did look at the .lst but I didn't see/understood the issue, nice work Richard! I know you've mostly moved on but please don't leave ;-)
/Henrik.
Charles says "I'll presume it's a bug and try to figure it out."
Let's wait.
I wonder if we could have same problem also without DEFINE RESET_ORG, just with code larger than 64k .....
i have never written a program that big with pbp , in fact if my code {excluding data fonts etc} got bigger than 16k would seriously think that a
8 bit pic with pbp is the wrong platform.
Warning I'm not a teacher
Bookmarks