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.

Sign up for GitHub

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

Jump to bottom

I/O order specifications #42

Closed
Wheatwizard opened this issue Sep 10, 2016 · 2 comments
Closed

I/O order specifications #42

Wheatwizard opened this issue Sep 10, 2016 · 2 comments
Labels
discussion

Comments

@Wheatwizard
Copy link
Collaborator

Lately we have had some changes in the way that input and output is ordered. We do not have a specification for the way that input and output is handled and I think we should.
@Wheatwizard
Copy link
Collaborator Author

Wheatwizard commented Sep 10, 2016 •
edited
Loading

The two things that I find important in I/O are the following

  • The empty program does not change the order
  • The top of the stack is printed first at the end of the program

These two requirements unambiguously force a I/O order. Thus I propose we use this order.

@DJMcMayhem
Copy link
Owner

This seems wrapped up as of V1.0.1 to me, so I'm gonna close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DJMcMayhem @Wheatwizard