prog8/docs/source/todo.rst

74 lines
5.4 KiB
ReStructuredText
Raw Normal View History

2018-08-06 01:35:43 +00:00
TODO
====
2022-01-19 20:37:27 +00:00
For next release
^^^^^^^^^^^^^^^^
2022-02-10 23:16:39 +00:00
- ...
2022-02-08 00:58:55 +00:00
2022-02-03 00:56:09 +00:00
2021-12-30 18:05:56 +00:00
Need help with
^^^^^^^^^^^^^^
- c128 target: various machine specific things (free zp locations, how banking works, getting the floating point routines working, ...)
- other targets such as Atari 800XL: all required details about the machine, I have no clue whatsoever
2022-02-01 20:34:17 +00:00
- see the :ref:`portingguide` for details on what information is needed.
2021-12-30 18:05:56 +00:00
Blocked by an official Commander-x16 r39 release
2021-11-13 11:56:59 +00:00
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2021-04-27 21:13:46 +00:00
- simplify cx16.joystick_get2() once this cx16 rom issue is resolved: https://github.com/commanderx16/x16-rom/issues/203
2021-12-30 18:05:56 +00:00
(I hope this will be included into the r39 roms when they get released)
2022-01-03 22:38:41 +00:00
Future Things and Ideas
^^^^^^^^^^^^^^^^^^^^^^^
2022-02-10 23:16:39 +00:00
Compiler:
- writeAssembly(): make it possible to actually get rid of the VarDecl nodes by fixing the rest of the code mentioned there.
2022-02-03 00:56:09 +00:00
- allow "xxx" * constexpr (where constexpr is not a number literal), now gives expression error not same type
- unify FunctioncallExpression + FunctioncallStatement and PipeExpression + Pipe statement classes, may require moving Expression/Statement into interfaces instead of abstract base classes
- for the pipe operator: recognise a placeholder (``?`` or ``%`` or ``_``) in a non-unary function call to allow non-unary functions in the chain; ``4 |> mkword(?, $44) |> print_uw``
2022-02-03 00:56:09 +00:00
- for the pipe operator: make it 100% syntactic sugar so there's no need for asm codegen like translatePipeExpression
2022-01-02 22:46:36 +00:00
- make it possible to inline non-asmsub routines that just contain a single statement (return, functioncall, assignment)
2022-02-10 23:16:39 +00:00
but this requires all identifiers in the inlined expression to be changed to fully scoped names.
If we can do that why not perhaps also able to inline multi-line subroutines? Why would it be limited to just 1 line? Maybe to protect against code bloat.
- simplifyConditionalExpression() should not split expression if it still results in stack-based evaluation, but how does it know?
- simplifyConditionalExpression() sometimes introduces needless assignment to r9 tempvar (scenario sought)
2022-01-03 22:38:41 +00:00
- consider adding McCarthy evaluation to shortcircuit and and or expressions. First do ifs by splitting them up? Then do expressions that compute a value?
2022-01-23 21:34:05 +00:00
- use more of Result<> and Either<> to handle errors/ nulls better?
- make it possible to use cpu opcodes such as 'nop' as variable names by prefixing all asm vars with something such as ``p8v_``? Or not worth it (most 3 letter opcodes as variables are nonsensical anyway)
then we can get rid of the instruction lists in the machinedefinitions as well?
2021-07-02 19:47:27 +00:00
- [problematic due to 64tass:] add a compiler option to not remove unused subroutines. this allows for building library programs. But this won't work with 64tass's .proc ...
Perhaps replace all uses of .proc/.pend by .block/.bend will fix that?
(but we lose the optimizing aspect of the assembler where it strips out unused code.
There's not really a dynamic switch possible as all assembly lib code is static and uses one or the other)
2022-02-10 23:16:39 +00:00
- Zig-like try-based error handling where the V flag could indicate error condition? and/or BRK to jump into monitor on failure? (has to set BRK vector for this)
- add special (u)word array type (or modifier?) that puts the array into memory as 2 separate byte-arrays 1 for LSB 1 for MSB -> allows for word arrays of length 256
2022-02-10 23:16:39 +00:00
Libraries:
2022-02-10 23:16:39 +00:00
- fix the problems in c128 target, and flesh out its libraries.
- c64: make the graphics.BITMAP_ADDRESS configurable (VIC banking)
- optimize several inner loops in gfx2 even further?
- add modes 2 and 3 to gfx2 (lowres 4 color and 16 color)?
- add a flood fill routine to gfx2?
- add a diskio.f_seek() routine for the Cx16 that uses its seek dos api? (only if that's stable)
Expressions:
- rethink the whole "isAugmentable" business. Because the way this is determined, should always also be exactly mirrorred in the AugmentableAssignmentAsmGen or you'll get a crash at code gen time.
- can we get rid of pieces of asmgen.AssignmentAsmGen by just reusing the AugmentableAssignment ? generated code should not suffer
2022-01-16 22:03:00 +00:00
- rewrite expression tree evaluation such that it doesn't use an eval stack but flatten the tree into linear code that uses a fixed number of predetermined value 'variables'?
2022-02-05 02:14:26 +00:00
"Three address code" was mentioned. https://en.wikipedia.org/wiki/Three-address_code
2022-02-03 00:56:09 +00:00
these variables have to be unique for each subroutine because they could otherwise be interfered with from irq routines etc.
2021-12-06 20:43:17 +00:00
- this removes the need for the BinExprSplitter? (which is problematic and very limited now)
2022-01-16 22:03:00 +00:00
and perhaps as well the assignment splitting in BeforeAsmAstChanger too
2022-02-10 23:16:39 +00:00
Optimizations:
- VariableAllocator: can we think of a smarter strategy for allocating variables into zeropage, rather than first-come-first-served
- translateFunctioncall() in BuiltinFunctionsAsmGen: should be able to assign parameters to a builtin function directly from register(s), this will make the use of a builtin function in a pipe expression more efficient without using a temporary variable
- translateNormalAssignment() -> better code gen for assigning boolean comparison expressions
- when a for loop's loopvariable isn't referenced in the body, and the iterations are known, replace the loop by a repeatloop
- automatically convert if statements that test for multiple values (if X==1 or X==2..) to if X in [1,2,..] statements, instead of just a warning.
2021-11-21 13:00:19 +00:00
- introduce byte-index operator to avoid index multiplications in loops over arrays? see github issue #4