Re:Parsing PHP in Go
by TazeTSchnitzel on Sunday July 27, 2014 @06:53PM
(#8094269)
There's also the problem of dealing with the standard library. Not everything has a directly equivalent function. So you'll make your app dependent on an obscure library based on another language's standard library.
[ Parent
| on HN ]
Re:Parsing PHP in Go
by jonathanyc on Sunday July 27, 2014 @09:32PM
(#8094681)
More advanced transformers even handle direct transformation of library calls to "native" library calls in the target language. I think it's mostly things that try to take advantage of syntax that is already pretty similar - Processing.js transforming from Java to JavaScript, for example, that decide it would be easier to do a relatively simple syntax transformation and then implement some sort of wrapper for function calls (as you describe) than to do a potentially more in depth and complicated transformation.