Path: csiph.com!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Hans-Peter Diettrich Newsgroups: comp.compilers Subject: Re: New experimental back end for C/C++ compiler targeting CLI Date: Tue, 30 Aug 2016 13:13:42 +0200 Organization: Compilers Central Lines: 20 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <16-08-013@comp.compilers> References: <16-08-007@comp.compilers> <16-08-008@comp.compilers> <16-08-009@comp.compilers> <16-08-011@comp.compilers> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: miucha.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="16509"; mail-complaints-to="abuse@iecc.com" Keywords: translator Posted-Date: 30 Aug 2016 09:59:01 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:1735 BartC schrieb: > On 29/08/2016 09:28, Hans-Peter Diettrich wrote: > Take, for example, a C-like language with //-comments to end of line. > Such a language is free-format so it could be written as one token per > line, with a comment on each line plus comments on their own lines. In the worst case the auther implemented a two-column layout, with a code block in the left and a comment block in the right column. Who'll know? > Even if translating to normalised code in the same language, it can be > challenging knowing where the comments are going to go. Even comment-based document generators often have problems with the unintended use of control tags by the coders. Even worse without such hints :-( DoDi