TODOs

Jump to bottom Edit New page

Martin Ruefenacht edited this page Feb 5, 2020 · 5 revisions

revamp regression
- cleaner/tests
- accept the weird macro situations
  - "skipping due to weird macros", checked by hand so far
  - MPI_Alloc_mem
  - MPI_Win_allocate
  - MPI_Win_allocate_shared
  - MPI_Win_shared_query
- allow plugin based architecture, find specials
  - find parameters with different names
  - find differing LIS types without whole diffing
- F08 POLY expressed causes name collision, not important for regression, but for comparison
  - how can we identify the polymorphic F08 bindings? there is no name difference...
revamp KIND system
- rename KINDs to reasonable/understandable names
- simple maps no longer capture everything required
- required refactor and rethink
pythonization
- the function parameter generation only for large variants abuses the postfix parameter
  - this was never the intention of this parameter
  - future rewrite with the KIND map system will need to move POLY ideas into the generators themselves
  - this abuses the POLY kinds to cause multiple function expressions and the postfix interpreted as the POLY flag
- the POLY expression needs to be moved done to generators
  - this will remove the need for the KIND maps as is
  - replace with a nicer to edit and more understandable system
  - this change will also allow testing POLY expression, not just the generator expression
chapter feedback
- state corrections, from prior to 4.x, they were wrong before we just replicated
- chapter 7 corrections, with changes to prior bindings, deferred until after pythonization
- pt2pt INDEX -> non-negative
- generally reduce KINDs, these are a lot of special cases, therefore shows complexity of our type system
nicer indentation through Latex
- MPI_Comm_spawn_multiple
  - array_of_commands, array_of_argv, linebreak without indentation
- MPI_Type_indexed
  - newtype parameter in LIS prototype is split to "new-\ntype"
    - just new line on comma, don't allow line breaking a parameter name
- MPI_Error_class is split by a two pages table
header generation
- constants and functions
- how do we do predefined functions?
  - they are defined in "english"
  - we just give straight C code?
lemonspotter
- integration (partially done) (functions were easy)
- typing is complicated from current KINDs