Difference between revisions of "Known Limitations"

From NARS2000
Jump to: navigation, search
(New page: == )SAVE With Non-Empty State Indicator == The decision to use a plain text ASCII file for saved workspaces has made it difficult to represent this case. For the moment, the interpreter ...)
 
Line 2: Line 2:
  
 
The decision to use a plain text ASCII file for saved workspaces has made it difficult to represent this case.  For the moment, the interpreter displays a message when saving a workspace with a non-empty SI, but I recognize that this problem needs to be solved.  Any suggestions?
 
The decision to use a plain text ASCII file for saved workspaces has made it difficult to represent this case.  For the moment, the interpreter displays a message when saving a workspace with a non-empty SI, but I recognize that this problem needs to be solved.  Any suggestions?
 +
 +
== Editing Suspended Functions ==
 +
 +
For the moment, the interpreter does not allow you to save a function being edited if it is suspended anywhere in the stack, even if it is the topmost suspended function.  The only recourse is to clear the suspension and then save the function.  This limitation needs to be relaxed to make the system more forgiving.
  
 
== No Help File ==
 
== No Help File ==
  
 
For the moment, I'm concentrating on putting all documentation into this Wiki, but I recognize that an offline help file (of some form) is necessary.  Any suggestions?
 
For the moment, I'm concentrating on putting all documentation into this Wiki, but I recognize that an offline help file (of some form) is necessary.  Any suggestions?

Revision as of 00:01, 18 April 2008

)SAVE With Non-Empty State Indicator

The decision to use a plain text ASCII file for saved workspaces has made it difficult to represent this case. For the moment, the interpreter displays a message when saving a workspace with a non-empty SI, but I recognize that this problem needs to be solved. Any suggestions?

Editing Suspended Functions

For the moment, the interpreter does not allow you to save a function being edited if it is suspended anywhere in the stack, even if it is the topmost suspended function. The only recourse is to clear the suspension and then save the function. This limitation needs to be relaxed to make the system more forgiving.

No Help File

For the moment, I'm concentrating on putting all documentation into this Wiki, but I recognize that an offline help file (of some form) is necessary. Any suggestions?