Corrode: C to Rust translator written in Haskell

Post by SilasX » Fri, Jul 08, 2016, 5:20 PM UTC

eridius wrote: post #60

SilasX wrote: post #55

Earlier quoted context omitted.

Well, it's just building off the same (negative) connotations of "Rust", which I think was itself a questionable name, trivial though it might seem. I've been looking at newer languages recently, and I see a lot of promise in Nim -- which renamed itself from Nimrod after users warned about what it connotes. Rust could take a cue.

Well, Rust isn't actually named after iron oxide. It's actually named after the fungus ( https://en.wikipedia.org/wiki/Rust_(fungus) ). Most people just don't know about the fungus.

Post by SilasX » Fri, Jul 08, 2016, 5:22 PM UTC

ape4 wrote: post #35

DanWaterworth wrote: post #26

Earlier quoted context omitted.

Here you go. It didn't like my stdio.h. Apparently enums and unions aren't supported, but: extern int printf(char *, ...); int main(int argc, char argv[]) { printf("Hello, world!\n"); return 0; } Was turned into: extern { fn printf(arg1 : *mut u8, ...) -> i32; } #[no_mangle] pub unsafe fn main(mut argc : i32, mut argv : *mut u8) -> i32 { printf(b"Hello, world!\n\0".as_ptr() as (*mut u8)); 0i32 } edit: Also worth noti…

Shouldn't a C `int` be converted to Rust's `isize`. I think that captures the spirit better.

Post by pshc » Fri, Jul 08, 2016, 5:40 PM UTC

SilasX wrote: post #63

ape4 wrote: post #35

Earlier quoted context omitted.

Shouldn't a C `int` be converted to Rust's `isize`. I think that captures the spirit better.

Not to look a gift horse in the mouth, but it seems like Corrode misses some other chances to use idiomatic Rust: 1. Rust fn:main doesn't need to return something. 2. The arguments to main aren't mutated, so Rust doesn't need to declare them as mutable. 3. Ditto for the argument to printf. Anyone know how easy it is to recognize and code for such cases in the transpiler? Edit: It looks like they might have opposite d…

Post by danidiaz » Fri, Jul 08, 2016, 5:44 PM UTC

Post by danidiaz » Fri, Jul 08, 2016, 5:53 PM UTC

ctb_mg wrote: post #66

pierrec wrote: post #32

I was curious about how this worked so I looked into the source a little (even though Haskell isn't exactly my cup of tea), and WOW... This is just amazing. The most important part of the source is highly educative literate haskell: https://github.com/jameysharp/corrode/blob/master/src/Langua...

As someone who knows zero haskell, and little markdown, can someone explain how this works? haskell.org [1] says there is "bird style" and "LaTeX style" ways of marking off code vs documentation, and I see neither in the linked file. Is it the "```haskell" blocks? [1] https://wiki.haskell.org/Literate_programming#Haskell_and_li...