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

consider forking c2nim instead #1

Open
stefantalpalaru opened this issue Jan 10, 2020 · 2 comments
Open

consider forking c2nim instead #1

stefantalpalaru opened this issue Jan 10, 2020 · 2 comments

Comments

@stefantalpalaru
Copy link

How about forking https://github.com/nim-lang/c2nim and gradually replacing its parsing with the Clang one? You would get a working program faster and you wouldn't have to re-discover all the Nim-specific workarounds that c2nim already implements.
@gogolxdong
Copy link
Owner

C/C++ project header files interleaves, one can end up with translating endless header files by hand. c2nim has to be enable to process header files recursively first.

@stefantalpalaru
Copy link
Author

So loop through them. Still not an excuse to reimplement most of c2nim from scratch.

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

No branches or pull requests
2 participants
@stefantalpalaru @gogolxdong