Path: csiph.com!news.mixmin.net!aioe.org!.POSTED!not-for-mail From: =?UTF-8?Q?Arne_Vajh=c3=b8j?= Newsgroups: comp.lang.java.programmer Subject: Re: is the java compiler written in c Date: Sun, 30 Aug 2015 22:03:09 -0400 Organization: Aioe.org NNTP Server Lines: 32 Message-ID: References: <893a1a37-881c-4e59-a069-38386dd1b0fd@googlegroups.com> <7b5d28de-2f30-4db7-aec7-03bd9ce81d00@googlegroups.com> NNTP-Posting-Host: NIM2IeSPVd0kE3mU1mieXw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.java.programmer:32441 On 8/21/2015 11:42 PM, BGB wrote: > On 8/21/2015 9:39 PM, Arne Vajhøj wrote: >> On 8/21/2015 5:51 PM, BGB wrote: >>> On 8/21/2015 2:15 AM, Eternal Hope wrote: >>>> >>>> On the one hand, any suggestion that the official C specification is >>>> 'tightened up' so that the almost endless 'undefined behaviors' are >>>> more >>>> rigidly defined is met with howls of protest because of the >>>> >>>> 'C is so powerful because you can do anything you want with it and >>>> that's the way we like it' >>> >>> you can tighten it up in a way which works on most targets, say, making >>> 'int' always be 32 bits, ... >> >> With C99 that should really not be necessary. >> > > possible, but this in-turn assumes you are using a compiler which > supports C99. > > C99 support is a little less widespread than targets which use a 32-bit > int. C99 compatible or almost C99 compilers are getting out there in most environments from PC and upwards. MSVC++, GCC, XLC, Solaris Studio, HP C etc.. Arne