Quote Originally Posted by skimask View Post
I based this off of Mr_E's simple print-string routine originally written for an LCD, adapted for my GLCD, now adapted to copy a string within the source over to a string array...basically so I can send it out with a serout or lcdout command.
You didn't get it from mister-e

While we're on the subject of optimization...
http://www.picbasic.co.uk/forum/showthread.php?p=30533

But really, this things got some serious shortcomings.

What if the person doesn't want a 255 byte string? Maybe they only need 32. Your routine will wipe out other variables well beyond the array.
What if they have more than 1 array? It only copies to an array called string.
What if they're using a 16F?
Why do they have to manually change MOVE?CW to MOVE?CN. Why not detect when PBPL is used, or have a separate macro for 32-bit addresses. Or better yet, do the tblrd's or EECON rd's manually, instead of relying on ReadCode. Then it's easy to handle over 64k or 16F's. Even without 2.50

Make it a true "PBP Extension".
<br>