Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • dynare dynare
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 110
    • Issues 110
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Dynare
  • dynaredynare
  • Issues
  • #96

Closed
Open
Created Feb 21, 2013 by Sébastien Villemot@sebastienOwner

Problem with struct2local.m

The function struct2local.m doesn't work as expected when a function exists in the path with the same name than a variable to be unpacked.

After the call to struct2local, MATLAB gives precedence to the function over the local variable.

This behavior is apparently in contradiction with the precedence rules described on: http://www.mathworks.com/access/helpdesk/help/techdoc/matlab_prog/f10-60956.html#

However it is present on most versions of MATLAB, and should be taken as a normal behavior of MATLAB.

A possible fix is to drop the use of struct2local, and to unpack structures by hand.

Assignee
Assign to
Time tracking