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

Is use of hsc2hs necessary? #3

Merged
merged 1 commit into from
Dec 16, 2013

Conversation

istathar
Copy link
Contributor

Strangest thing. I went to all the trouble to hack support for .hsc files into my build wrapper, then started looking at what the output from hsc2hs happened to be, and discovered it was essentially ... the same.

From which I realized that FFI works without requiring the hsc2hs preprocessor, at least it appears to. So for the hell of it I stripped out the use of hsc2hs and converted .hsc.hs and gave make test a go. Somewhat to my surprise, it built and checked.

Makes for an annoying diff off the command line because of Git's pathologically useless approach to file renames; something GitHub presents better.

AfC

christian-marie pushed a commit that referenced this pull request Dec 16, 2013
Is use of hsc2hs necessary?
@christian-marie christian-marie merged commit b03a7ef into christian-marie:master Dec 16, 2013
@christian-marie
Copy link
Owner

You are correct! hsc2hs allows us to use it's preprocessor things like peek and sizeof to write haskell for attributes pulled out of headers and such. So far though, I've managed to get away with opaque references everywhere. Thus, never actually made use of it.

If we've gotten this far without, I don't see us needing it.

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

Successfully merging this pull request may close these issues.

2 participants