Re:C to Java Translation. Automatic, Complete, Correct. Free...
by emsy on Wednesday April 29, 2015 @08:12AM
(#9457683)
The main problem being undefined behaviour that is actually undefined and varies from compiler to compiler!
[ Parent
| on HN ]
Re:C to Java Translation. Automatic, Complete, Correct. Free...
by raverbashing on Wednesday April 29, 2015 @08:31AM
(#9457777)
Yeah, you might need a config switch to configure what would you want to do with the most common undefined behaviours (or "just change" your C code)
(Because "just change" usually ends up creating other problems. Been there, done that, "code is wrong but works" and when you try to fix stuff breaks)
Re:C to Java Translation. Automatic, Complete, Correct. Free...
by TorKlingberg on Wednesday April 29, 2015 @09:18AM
(#9458029)
You are free to assume that undefined behavior never happens. Unless you want to support invalid c programs.