Feature Requests

From VpriWiki

Jump to: navigation, search

Add your suggestions for improvements to the system to the list below. If the idea isn't obvious and needs more than a one-sentence explanation, or if you need to illustrate the idea with use cases, scenarios, etc., then please create a new page for your suggestion and make a short entry in the list below that links to it.

Feel free to insert items anywhere in the list, reflecting the importance of the suggestion with the most urgent item nearest the top.

  • Make type definition allocate space for fields (fixed ikp 2008-06-17 svn 426)
  • Pepsi debugging: interrupt, inspect global and local variables, single step, print object contents, stack frames, etc.
  • Jolt debugging: see Pepsi debugging.
  • Better dlopen error reporting (see email from tak "[fonc] Compile idst with SELinux" on "Thu, Apr 3, 2008 at 12:27 AM")
  • Make libjolt compile again (see patches from M. FIG -- first "[fonc] Compilation problem: undefined reference to `GC_malloc'" on "Thu, Nov 22, 2007 at 6:40 PM" -- most recent "[fonc] [PATCH 01 of 10] Get libjolt working again" on "Tue, Mar 11, 2008 at 9:42 PM")
  • Minimal Documentation
  • static code generation
  • Dynamic pepsi compiler (i.e., compile Pepsi to jolt instead of C)
  • Namespaces
  • Non-local control (e.g. exceptions, setjmp)
  • Jolt constant objects (quoted lists, etc.) should be immutable
  • "Understanding" C header files (structure size/layout, constants, types etc.) for accessing outside libraries (e.g. OS-level services, windowing/events, etc.) from Jolt
  • Solve the "boot.k" problem, where selective pieces of boot.k must currently be pasted into various applications (see libjolt/Makefile for example).
  • Automatic storage (dirt-cheap and scoped memory allocation) in Jolt (e.g. alloca)
  • Jolt ARM code generation (current proof-of-concept has significant performance issues)
  • GC memory consumption needs to be capped
  • C blocks are not possible within Pepsi blocks
  • Generated code should be garbage collected
  • "selector-centric" dispatch (ala multimethods)
  • Memory debugging (for segfaults in Jolt)
  • Performance profiling (only very basic support needed)
  • Floating point support in Jolt
  • Primitive types in Jolt (signed, unsigned, float, vector, etc.) (?)
  • SIMD support in Jolt
  • Fix 32-bit word assumptions in Jolt
  • OS-level multi-threading
  • Green multi-threading
Retrieved from "http://www.vpri.org/fonc_wiki/index.php/Feature_Requests"
Personal tools