Block rewriting with Clang
techtalk.intersec.com
Block rewriting with Clang
1–10 of 23 posts
Re: Block rewriting with Clang
#2While kudos to getting this to work, seems like a huge amount of effort and voodoo when instead one could have used a different language in the first place.
Re: Block rewriting with Clang
#3I wonder what it would have taken to start contributing blocks support to GCC.
Re: Block rewriting with Clang
#4While kudos to getting this to work, seems like a huge amount of effort and voodoo when instead one could have used a different language in the first place.
I'm not sure why you're getting downvoted. Your opinion seems valid to me. Many of the benefits to writing C go away if you use extensions like this.
Re: Block rewriting with Clang
#5While kudos to getting this to work, seems like a huge amount of effort and voodoo when instead one could have used a different language in the first place.
What language would you happen that has both ridiculous portability (you can use it from any language) and performance? Sounds like a fairy tale to me.
Re: Block rewriting with Clang
#6While kudos to getting this to work, seems like a huge amount of effort and voodoo when instead one could have used a different language in the first place.
What language would you happen that has both ridiculous portability (you can use it from any language) and performance? Sounds like a fairy tale to me.
Languages such as Go, Rust or Swift aim to fill that gap, but in 2010 they were either nascent or simply inexistent.
Re: Block rewriting with Clang
#7While kudos to getting this to work, seems like a huge amount of effort and voodoo when instead one could have used a different language in the first place.
Thanks. That said, I'm not sure the amount of effort is that huge: having a working rewriter was a matter of days, which makes it far less expensive than rewriting a codebase of several hundreds of thousands of C to a new language.
Re: Block rewriting with Clang
#8I wonder what it would have taken to start contributing blocks support to GCC.
Some already tried:
http://anzwix.com/a/FreeBSD/GccAddSupportForApplesBlockExten...
http://gcc.1065356.n5.nabble.com/RFC-Apple-Blocks-extension-...
I'm not aware of any attempt that successfully reached the upstream. GCC could have simply imported Apple patches if there were no licensing issues.
Re: Block rewriting with Clang
#9Earlier quoted context omitted.
What language would you happen that has both ridiculous portability (you can use it from any language) and performance? Sounds like a fairy tale to me.
Languages such as Go, Rust or Swift aim to fill that gap, but in 2010 they were either nascent or simply inexistent.
Go doesn't embed at all, so right there that's out.
Rust is still very unstable, and I wouldn't recommend it for production use.
I'm not sure why you would use Swift unless you're targeting iOS, it seems like a terrible idea to base your code on proprietary languages without ridiculous, .NET levels of support. I also don't believe swift is easily embedded with its huge runtime ass.
Re: Block rewriting with Clang
#10Earlier quoted context omitted.
What language would you happen that has both ridiculous portability (you can use it from any language) and performance? Sounds like a fairy tale to me.
Languages such as Go, Rust or Swift aim to fill that gap, but in 2010 they were either nascent or simply inexistent.
D? why does everybody hate/ignore D?