Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Libraries can be inserted in theirselve and written to file system #563

Open
franzlst opened this issue Apr 17, 2020 · 3 comments
Open

Libraries can be inserted in theirselve and written to file system #563

franzlst opened this issue Apr 17, 2020 · 3 comments

Comments

@franzlst
Copy link
Member

A library can be dragged into itself. This of course causes recursion issues if saved to the file system and loaded again.

Originally created by @franzlst (Franz.Steinmetz@dlr.de) at 2018-07-23 13:32:17+00:00 (moved from RMC internal repository)

@franzlst
Copy link
Member Author

My solution to this would be:

  • preserve it while storing
  • and only give a warning while editing

So the user could do such things to generate wrapper libraries and so the user should not be hold back to work as they wanna.

@franzlst and @sebastian-brunner What are your thoughts about this?

Originally created by @Rbelder at 2018-07-24 16:09:52+00:00 (moved from RMC internal repository)

@franzlst
Copy link
Member Author

I would omit recursive libraries. In general, this is only possible if we allow for on the fly loading of states during execution.

Originally created by @sebastian-brunner (Sebastian.Brunner@dlr.de) at 2018-12-12 14:47:12+00:00 (moved from RMC internal repository)

@franzlst
Copy link
Member Author

So as long as you can not store them it is omitted I think. So that is what the comment of me was about.

Originally created by @Rbelder at 2018-12-12 17:32:38+00:00 (moved from RMC internal repository)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants