Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.compilers > #1731
| From | Hans-Peter Diettrich <DrDiettrich1@netscape.net> |
|---|---|
| Newsgroups | comp.compilers |
| Subject | Re: New experimental back end for C/C++ compiler targeting CLI |
| Date | 2016-08-29 10:28 +0200 |
| Organization | Compilers Central |
| Message-ID | <16-08-009@comp.compilers> (permalink) |
| References | <16-08-007@comp.compilers> <16-08-008@comp.compilers> |
rockbrentwood@gmail.com schrieb: > A really good source-to-source compiler should also be making proper > adjustments to the comments. That may even entail a degree of natural language > processing! Except for the "may" part. Such problems occur only on source-to-source translation, where the output should be human readable. A compilation into instructions of a physical or virtual machine does not necessarily include comments, and decompilation of executable code doesn't have to deal with comments at all. Programming language translations are possible only for sufficiently similar languages. If you look inside the "original VB" to MSIL translation (not VB.NET), you'll find horrible constructs for the implementation of the Basic ON ERROR... statements, even if both languages are imperative. In a source-to-source translation I'd not try to process comments, except for structural parts like XML or doxygen tags. In my C to Pascal converter I encountered many problems, not related to control flow. I found most challenging the decisions, which parts of the input should be "copied" unchanged, and which parts have to be interpreted, i.e. must be broken down into more basic constructs. Even if both language have equivalent control structures, like switch statements, these may be semantically so different, that a direct mapping is not always possible. The same for preprocessor statements - can/should they be translated into equivalent high-level contstructs of the target language, or do they have to be expanded before a translation? DoDi
Back to comp.compilers | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
New experimental back end for C/C++ compiler targeting CLI Alexandre <alebencz@gmail.com> - 2016-08-25 10:40 -0300
Re: New experimental back end for C/C++ compiler targeting CLI rockbrentwood@gmail.com - 2016-08-26 12:54 -0700
Re: New experimental back end for C/C++ compiler targeting CLI Hans-Peter Diettrich <DrDiettrich1@netscape.net> - 2016-08-29 10:28 +0200
Re: New experimental back end for C/C++ compiler targeting CLI BartC <bc@freeuk.com> - 2016-08-29 18:52 +0100
Re: New experimental back end for C/C++ compiler targeting CLI Walter Banks <walter@bytecraft.com> - 2016-08-29 21:21 -0400
Re: New experimental back end for C/C++ compiler targeting CLI Walter Banks <walter@bytecraft.com> - 2016-08-30 13:44 -0400
Re: New experimental back end for C/C++ compiler targeting CLI BartC <bc@freeuk.com> - 2016-08-30 22:48 +0100
Re: New experimental back end for C/C++ compiler targeting CLI Walter Banks <walter@bytecraft.com> - 2016-08-31 13:24 -0400
Re: New experimental back end for C/C++ compiler targeting CLI Martin Ward <martin@gkc.org.uk> - 2016-09-06 18:09 +0100
Re: New experimental back end for C/C++ compiler targeting CLI Hans-Peter Diettrich <DrDiettrich1@netscape.net> - 2016-08-30 13:13 +0200
Re: New experimental back end for C/C++ compiler targeting CLI Walter Banks <walter@bytecraft.com> - 2016-08-29 13:15 -0400
csiph-web