Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
A string bug in 1.2.8-s682 (*solved*)
#3
boriel Wrote:Thanks for your bug reporting. I will check it this evening.
Also, I notice you #include <alloc.bas> but this is not needed for your code. Maybe you are planning to use it later?
Anyway: I'll check it this evening (have others bugs pending to be fixed) :roll:
Your welcome. I was planing to use it for later but I have since rem-ed out.
I have also changed the ORG address from 39680 to 40704 and removed
--strict-bool. If I where to use double buffering then the second screen would
sit in uncontended memory for speed at address 32768 to 39679 and then
there is 1KiB for the stack and that brings us to address 40704. Then there
is 23KiB for program and data followed by 1280 (1.25 KiB) for the heap and
that brings the address up to 65536 or fully used memory except for 8KiBs
of lower contended memory that is not used. That get's me to my point.
It would be good if I could place non speed critical sections of my program
below the ORG address for e.x.: Sub Foo at Low....End sub. Then low would
be a #Define. For this case, Low would be 32767 then the compiler would
compile a Sub or a Function, get the complied length of it and do a Low -
Length and place it at that address and then update (decrement) Low
accordingly and so on until all the Subs and Functions that were marked
with "at Low" are compiled.

Also, if I specify the output file as GAME.TAP then GAME.TAP shows up
in the byte header instead of stripping the extension out causing me to
do a rename from the .BAT file. What was the option (--) for the ROM
print routines and has it be taken out? If so why? Last it would be nice to
have a PutChar (8x8 pixels) at graphics coordinates in the library, clipping
supported for the edges of the screen and Attr supported and a routine with
Attr support stripped out of it.

I do not think string slicing works as supposed but I have not checked it
since 1.2.6 and that's it for now.

I do hope that you find out what the problem is because this is unusable.

Thanks you,

Darkstar.
Reply


Messages In This Thread

Forum Jump:


Users browsing this thread: 3 Guest(s)