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

The pywriter is a mess #19

Open
sebastianriese opened this issue Sep 6, 2013 · 1 comment
Open

The pywriter is a mess #19

sebastianriese opened this issue Sep 6, 2013 · 1 comment
Milestone

Comments

@sebastianriese
Copy link
Owner

The pywriter is in many places inelegant, error prone and difficult to understand.

The implementation of generation options is completely ad-hoc and hard to follow, this should be replaced by an elegant, extensible and clear general mechanism.

Preferably on assembles a Composite, each of which components represents an option. Then the correct code is written automagically.

@sebastianriese
Copy link
Owner Author

The messiness of the pywriter has been mitigated by factoring out the Parser and Lexer standard implementations to a runtime library. Yet is it still not good and will get worse again, as soon as mapping via multitables will be implemented.

@sebastianriese sebastianriese added this to the v0.1.0 milestone Oct 24, 2016
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