Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!goblin3!goblin.stu.neva.ru!exi-transit.telstra.net!news.telstra.net!exi-spool.telstra.net!exi-reader.telstra.net!not-for-mail Date: Thu, 26 May 2011 18:34:54 +1000 From: Esmond Pitt Reply-To: not.esmond.pitt@not.bigpond.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 Newsgroups: comp.lang.java.programmer Subject: Re: Java generics and type erasure References: <9d4c2b16-beb5-40b1-87a2-f03e971efeed@k17g2000vbn.googlegroups.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Lines: 11 Message-ID: <4dde10b0$0$67777$c30e37c6@exi-reader.telstra.net> NNTP-Posting-Host: 120.151.14.51 X-Trace: 1306398896 exi-reader.telstra.net 67777 120.151.14.51:44842 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4594 On 26/05/2011 4:48 PM, Lawrence D'Oliveiro wrote: >> No -- presumably, it would have caused problems compiling 1.4 source code >> against 1.5's libraries, not running existing 1.4 bytecode linked to 1.5 >> libraries. > > In Java terms, what’s the difference? The difference is that generic type-signatures are present in .class files for compilation purposes even though generics are erased to their lower bounds at runtime, so that the compiler can enforce the semantics of generics.