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

Document design principles #1

Open
ftomassetti opened this issue Aug 22, 2019 · 0 comments
Open

Document design principles #1

ftomassetti opened this issue Aug 22, 2019 · 0 comments

Comments

@ftomassetti
Copy link
Contributor

One important principle is the pragmatic approach: our goal is not to replicate the exact some behavior of the RPG compiler running on the mainframe. It would be extremely hard to support the exact way that mathematical operation behave or to replicate exactly the way data is stored in memory. We are not aiming to doing that. We aim instead to get equivalent behavior for all reasonably common usage patterns.

For example, if somewhere there is a program performing tricks with packed numerical data and the overlay directive, then it should not be expected to work. Ideally an error or a warning should be triggered by the compiler.

This and other principles should be documented in the project and we should add examples and explanations as we take more design decisions.

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

No branches or pull requests

1 participant