Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: "Rod Pemberton" Newsgroups: comp.lang.misc Subject: Re: Wirth-ian languages Date: Tue, 29 Apr 2014 07:41:24 -0400 Organization: Aioe.org NNTP Server Lines: 22 Message-ID: References: <20140428111524.742@kylheku.com> <94y7v.153301$AI5.43400@fx32.am4> <20140428125523.803@kylheku.com> <57B7v.161805$Qm2.151455@fx16.am4> NNTP-Posting-Host: CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Opera Mail/12.16 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.misc:2061 On Tue, 29 Apr 2014 06:33:50 -0400, James Harris wrote: > If you did choose to evolve C into something else you would > probably not want to keep it backwards compatible. Why wouldn't you? 1) C is everywhere 2) if the C compiler has a preprocessor, you can do most any syntax conversion 3) C can do everything, or C++ can if C can't, and C++ was coded in C ... LOL. ;-) AISI, the easy place to start is to write your language parser in C. Yes, you may need to rewrite it in the host language, eventually, or you could cross-compile. Rod Pemberton