Known Issues

⚠️ Please remember that the Blitzmax Language Server is not fully operational and most of the features are experimental.

FEATURES

• Diagnostics
  • Experimental feature
  • Further work is required to add decent messages
• Outline (Document Symbols)
  • AST view is incomplete
• Workspace Symbols
  • Experimental feature

FUNCTIONALITY

• Progress Bars do not work.
  • 9/12/21: Progress bars are not currently supported by VSCODE
  • Client does not send a workDone token during Initialise.
    • 22/11/21, it appears that workdone tokens are not sent in initialise event unless they are enabled in the client using a progressOnInitialization client option.
    • See: https://github.com/microsoft/language-server-protocol/issues/904
• textDocument/documentSymbol taking 11 seconds because I am parsing workspace
  • Need a progress bar, but there is currently no support for them in VSCODE
• Workspace symbols return all symbols for all workspaces
  • This is a workaround because the LSP does not yet define a workspace uri in the workspace/symbols request.
    • Logged as an issue but LSP developers see this as a low priority issue.
• Shutdown messages are not always send and can cause language server to remain open.

BUGS

• PARSER FAILSAFE VIOLATION

  • "=" sign (Default value) in function/method argument
  • Byte Ptr as a datatype in function/method argument
  • Abstract Methods
  • By reference "var" without datatype Function XYZ( param var )
  • Array Function arguments Function XYZ( param:String[] )

• PARSER

  • FOR NEXT does not parse correctly.
  • Compiler directives like this one cause a FAILSAFE violation ?bmxng Function _loadCallback:Size_T(buffer:Byte Ptr, buflen:Size_T, data:TStream) ?Not bmxng Function _loadCallback:Int(buffer:Byte Ptr, buflen:Int, data:TStream) ? Return data.Read(buffer, buflen) End Function