Developer's Notes
The topics in red (in no particular order) cover some of the areas that need documentation and or source-code implementation, i.e. no NARS wiki page yet exists for the topic(s). See also NARS Project Ideas. Feel free to add to the list as you may find appropriate. The topics in blue/purple are Developer Notes which have been initiated or at least partially and sometimes fully documented. The word "developer" as used on this wiki page generally refers primarily to APL Interpreter developers, particularly C programmers or persons interested in learning/programming in C; however, APL Developers and Programmers are preeminently also invited to submit topics on this wiki page for consideration, review, implementation, etc. See also NARS Discussion Forum.
[Listed below: Task/wiki page - status(if available). Description/explanation]
- Symbol and Hash Tables - wiki page created. Requires further development
- Intellisense - Trie Auto-Completion - keyboard, autocompletion for APL variable names, function names, labels - contextually relevant suggestions, e.g. Tab-key selected
- Datatypes and Storage
- State Indicator
- Function Storage
- Parser
- Display and Formatting
- Saved Workspace Structure
- Building An Executable - completed. Building a NARS2000.exe file on your local machine using the latest source code version available at SourceForge.net
- Another Approach To Building - outdated/potentially obsolete, requires update and or integration.
- Creating New System Functions - in process. Creating new "quad" ⎕ system functions for NARS2000.exe
- Debugging
- Committing Changes
- Reference Counts
- Tokens
- Macros
- Magic Functions
- VirtualAlloc vs. GlobalAlloc
- RESDEBUG Cover Functions
- Per Tab Data
- Unicode/Wide Chars
- Undo Buffer
- Translation on Copy/Paste
- Source File Formats
- Programming Practices
- Threads and Thread Local Storage
- Window Hierarchy
