Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • mbdyn mbdyn
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • DAER
  • mbdynmbdyn
  • Issues
  • #61

Closed
Open
Created Nov 13, 2020 by Pierangelo Masarati@10102934Maintainer

Inconsistencies and too little info in error messages from math parser

The math parser is often very little informative and inconsistent about errors in expressions. For example, using an undefined variable like this set: 2*x; gives "(unexpected token) at line 1", whereas set: x*2; correctly gives "(unable to find variable "default::x") at line 1". A thorough revision would be advisable.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking