Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!fu-berlin.de!uni-berlin.de!news.dfncis.de!not-for-mail From: "H.J. Sander Bruggink" Newsgroups: comp.lang.java.programmer Subject: Re: =?UTF-8?B?QW5kcm9pZOKAlFdoeSBEYWx2aWs/?= Date: Mon, 06 Jun 2011 11:21:40 +0200 Lines: 25 Message-ID: <953kh4Fo65U1@mid.dfncis.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: news.dfncis.de D/UzioCxUmFquBN2KR6kjwK83xNlGfPCnMwMAw24uRJGZa User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10 In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:5008 On 06/04/2011 06:08 AM, Lawrence D'Oliveiro wrote: > Most languages (including Java) that claim to be “portable” seem to be > implemented in C. Therefore they can only be ported to platforms where a C > compiler (or cross-compiler) is already available. Therefore, > > Portability(all such languages) ⊆ Portability(C) > > or even > > Portability(all such languages apart from C) ⊂ Portability(C) The fact that there exist platforms on which there is no JVM, indicates that porting a C (or C++) program to a different platform is not simply a recompile. There is actually a big effort involved. C is very portable, yes, if you're writing a single-threaded, non-networking console application. If you want the program to be actually usable in practice, you need platform-independent libraries for the networking, the threads, the GUI, the XML processing, etc. And once you've decided which ones to use, the amount of platforms your C program compiles on without a rewrite is typically /less/ than the amount of platforms a Java program runs on. groente -- Sander